4 ms·
> Umm... why would you not choose a relational engine to start with? There's typically two answers to this question: When they first started things were chang
by CSMastermind 3y ago
> Umm... why would you not choose a relational engine to start with?
There's typically two answers to this question:
When they first started things were changing so quickly they didn't want to commit to a schema and felt like doing real data modeling would slow their velocity down so they dumped everything into Mongo and called it a day.
Or they had someone on the team who insisted that Nosql was the way to go. They'll say something like, "I worked on xyz team at Amazon and we just used DocumentDB for everything and never had a problem. Those horror stories about Mongo are all from people who didn't use it right."
- jacobyoder 2y agoInterestingly... I've never encountered the first scenario as a justification. I know it must exist, as I've read people describe it. Every time I've been in a group where nosql was desired, it was because they saw it at a conference, or watched a youtube video, or read some blog extolling nosql virtues, and... yeah - that second option. They'd either never actually used nosql, or didn't realize what they were getting into, possibly because even if they'd used it, the larger architecture had SQL in it someplace, just outside what they could see.