Re:Startup Engineers and Our Mistakes with MongoDB
by nulagrithom on Thursday July 20, 2017 @11:20AM
(#14813235)
> I don't do complex 10 way joins for apps.
That hits home. There's a lot of this in the legacy code base, and yeah, it's painful.
Interesting approach. Thanks for the discussion. I'll have to ponder this a while.
Even if I were using a relational database, I would still separate out my different domains (drivers, terminals, stops, etc.) into different classes/microservices and join the different entities in memory.
This would allow different developers, teams etc. to focus on separate business objects and would allow you to start off with a monolithic code base/app and separate the app out to microservice later without intertwined logic and to mix and match storage based on what makes sense.
I never said always embed everything into one document. I said think through your aggregate roots to decide how to design your apps and your document model.
I've designed this way for the last 10 years - 9 using RDMSs. I don't do complex 10 way joins for apps. I separate out business domain logically and let each module be responsible for its own domain and then have an overarching orchestrating class that combines the various objects when needed.