3 ms·
I was thinking something along these lines, as well. I recently learned of the IDesign Method, which seems to try to do something like this, with a standard ar
by holtalanm 8y ago
I was thinking something along these lines, as well. I recently learned of the IDesign Method, which seems to try to do something like this, with a standard architecture for handling scaling in a future-proof kind of way.
Forgive me if my understanding of that architecture is wrong. I only have read parts of the book so far.
- scarface74 8y agoIt's basically Domain Driven Design combined with SOLID principals. If you have a Customer domain and an Order domain, as tempting as it is to join the two related tables in code, avoid it. Have another service (not http service/domain service) aggregate information from both domains. It's then mechanically trivial to split the Customer module and the Orders module both the code and the data store.