4 ms·
You nailed it. I think the issue is that people don't know what questions to ask when gathering the requirements. I'd like to know more about how this part of
by trimbo 13y ago
You nailed it. I think the issue is that people don't know what questions to ask when gathering the requirements.
I'd like to know more about how this part of the article came to be:
"This choice was made early on and it was supposed to be a temporary one."
HOW was that choice made. What requirements were out there. I think too many people choose Mongo because they believe it's "schemaless"[1] and faster for development, but don't look at the requirements for their actual use case.
[1] - There's always a schema. Either it's informally defined by your code or represented formally somewhere else.
- relistan 13y agoIt was one of those, "we need to do something now and this will work" solutions. We had a really talented consultant working for us, writing some of the early code. He was familiar with Mongo and wanted to go that route. Early on I said we should use Cassandra for this, but it took us quite some time to get to the point of being able to migrate. A testament to his code and the "this will be temporary" foreknowledge is the fact that we could swap data stores in a pretty massive sense without much in the way of outward-facing changes to our processing engine. I think the hard thing for us up front was that trying to explain Cassandra data models to someone (and this guy is really really good) and then hand the rest of the work over to them to implement now, on a contracting rate is not a trivial problem. And we needed to hurry for both deadlines and burn rate.
- trimbo 13y agoCool, thanks for the info!