3 ms·

I work in ERP space, which is the ultimate uncool from typical HN perspective; but sometimes "uncool" has a Venn diagram overlap with "mature". A modern top ti

I work in ERP space, which is the ultimate uncool from typical HN perspective; but sometimes "uncool" has a Venn diagram overlap with "mature". A modern top tier RDBMS is an incredibly powerful, fast, mature, stable tool - when wielded wisely by the knowledgeable wizard. To be fair, the developers must have a solid understanding of programming language, and business domain, and SQL / data dictionary / ERD - which I've always taken for granted but eventually realized is not the norm.

mamcx 3y ago
I also work on this space, and kind of see the value of this idea. Having a log store make sense, and having a super-VIEW replacement that can re-compute the data (so I can denormalize o build secondary tables/indexes that could or not be stored) is a common pattern. That is fine. What is NOT fine, and that normal DBS avoid, is to add "eventual consistency". I NEED to get exact counts, sum, avg, and RIGTH NOW, not a second later. The more "eventual" the data become the worse things are, and that is the major way to add bugs and problems. One of the reasons FK are important is they eliminate the chance of getting the relationships wrong, but also, to get it right NOW.