4 ms·
It is surprising how often all these things get reduced to bunch of relational tables with slightly non trivial integrity constraints because sooner than later
by dfox 10y ago
It is surprising how often all these things get reduced to bunch of relational tables with slightly non trivial integrity constraints because sooner than later there will be something that is outside of normal bussiness processes and thus requires exceptions in all these rules.
Essentially all big ERP packages follow the model of bunch of relational tables directly exposed to user with bussiness rules and processes as an afterthough. One can say that this stems from historical reasons, but unforeseen usecases that have to be somehow handled right now are also significant reason.
- UK-AL 10y agoHaving worked on ERP systems, I find the dB often becomes a major bottleneck because of this reason. You end up creating a really beefy single database, with tons of ram, infinityio etc We have a bunch of different DBs for specific purposes. Some have to be super fast for reading, some just store streams of events, others need to maintain consistency.