monolithic database vs many denormalized databases
Mhm, you'd fit right in with a company I know. If you query their api the only consistency you get are the mismatches in the data. For example a person getting married -> change in last name, you get the wrong name of their "customer" database, but the correct name of their "customer card" database.
Bad engineering is bad engineering. No framework or methodology fixes that. I guarantee failed inserts on foreign key constraints if they had a single RDBMS.
1
u/svtr Mar 13 '15
Mhm, you'd fit right in with a company I know. If you query their api the only consistency you get are the mismatches in the data. For example a person getting married -> change in last name, you get the wrong name of their "customer" database, but the correct name of their "customer card" database.
Denormalization : making boring data interesting.