Geek asks and answers

Referential data integrity between services

In SOA, I was confused by the fact that a service that works with data from different databases or even using different services can have referential integrity to duplicate data across databases or services.

For example, you have a user table in some kind of authentication database, and you want to reuse this user information in another database. You also want this user entry to exist in the authentication database. Suppose you want to associate a user account in an authentication database with a news article in another database. How it's done? How do you do this using something like LDAP?

If the authentication information was contained in the same database, only in a different table, I could see how you can simply use foreign keys to create a link between the news article and the user account.

I am trying to find answers to this problem, but I have to use the wrong phrases because I do not come up with anything useful.

+5
source share
1 answer

Some platforms allow foreign key restrictions between databases, and some do not. If you need referential integrity between databases, you need to choose a platform that supports it. Normalization - another problem - never says, "Move these columns to another database."

. ( , .)

"multi-tenant"; , . MSDN .

+1

More articles:


All Articles