3 ms·
If you're not going to couple any business logic to the persistence layer, then what the hell is the point of using a RDBMS?
by M_Bakhtiari 8y ago
If you're not going to couple any business logic to the persistence layer, then what the hell is the point of using a RDBMS?
- Anchor 8y agoData consistency with concurrency (transactions).
- M_Bakhtiari 8y agoWhat is your data supposed to be consistent with, then?
- michaelmcmillan 8y agoYour reply suggests you either couple everything or nothing. It’s more nuanced than that. Everything is a trade off. With that said, it looks like this library will position itself in the center of your architecture — and I would be very hesitant to do that.
- M_Bakhtiari 8y agoOf course anyone should be hesitant to over-model the business domain in any part of the application including the database, but the entire reason of existence of the RDBMS is to maintain consistency with something, and if that something isn't the business domain, then what good does it do?
- michaelmcmillan 8y agoI don't know where over-modeling fits in the argument. Business logic in an isolated part of an application is likely to age better than something that is intertwined with a database or other external dependencies.