Re:A one-size-fits-all database doesn't fit anyone
by diroussel on Wednesday June 27, 2018 @04:31PM
(#17411586)
Do relational databases really give you consistency? They can do if you are careful how you write your app. And many people don't use serialisable transactions because of the implications.
Also relation databases enforce their version of consistency. What if I only want consistency within one customer's data but not all customers?
I could have two inserts for operations on two different customers fail because of a deadlock on page slips in a secondary index. I didn't need that consistency but the database didn't know that.
These things always depend on business requirements. What relational database offers, above all others, is data consistency: if used properly, it's an incredibly useful safety net that prevents you from errors that corrupt user's data. Transactions and especially proper schema can catch a lot of bugs that could otherwise wreak havock.
So, it's a trade-off: how bad, from a business perspective, would some data corruption be? If you're Tinder, mixing up profile information or deleting a match is probably not that bad. If you're dealing with other people's money, on the other hand, it could destroy your entire business.