SOA design principles with regards to database relationships

Posted by Eitan on Stack Overflow See other posts from Stack Overflow or by Eitan
Published on 2010-06-08T08:31:43Z Indexed on 2010/06/08 8:32 UTC
Read the original article Hit count: 334

If I were to extricate my current membership provider from my solution, i.e. as a dll and expose it as a web service with it's own db, how would I model the relationships with regards to SOA design.

For example

I have a table:

USER id, name, lastname, username, password, role.

and table

PRODUCT id, name, price, createdate, userid

the foreign key being userid to table user.

How would I model the relationship and/or query the db.

If I wanted to get all products that were uploaded today for example, before I would query:

SELECT u.name, u.lastname, u.username, p.* FROM PRODUCT p INNER JOIN USER u ON p.userid = u.id WHERE createdate = '05/05/2010'

Now that I don't have the table within the database how would I perform this query?

Thanks.

© Stack Overflow or respective owner

Related posts about membership

Related posts about soa