4 ms·
> a single service having multiple data layers for different things isn't really a big operational or organizational problem. Your statement is true, and I’d l
by nthj 6y ago
> a single service having multiple data layers for different things isn't really a big operational or organizational problem.
Your statement is true, and I’d like to consider the product/feature side as well. Enterprise SAAS customers expect their Single Source of Truth to be, well, a single source. They want reports across all of the data they have put into a product. A feature that should be a couple of JOINs can quickly become pretty dicey when data is sliced across multiple data stores.
- Pamar 6y agoThis is exactly what always made me very skeptical about microservices (as I said, no actual experience so I might just change my mind if I start using them) - for any non-trivial problem reasoning about your data in a integrated and coherent way seems pretty daunting.
- still_grokking 6y agoFor that reason people employ "data warehouse" systems and architectures. Microservices aren't complete without that complexity.
- Pamar 6y agoMy problem with this approach is that my system basically handles a complex inventory and allows complex orders out if it, orders you can modify/update/cancel over a very long (months) period. So we do have data warehouse for strategic analysis and planning, but we need to also manage complex data which has to be consistent and available 24/7.
- PeterisP 6y agoYou push the data from all the microservices to a single data warehouse and do the reporting from there - so all the aspects that modify the data are microservices, but the reporting is based on a data storage monolith.