3 ms·
I just don't like the "right tool for the job" argument. Then say the "right technology for the task" then. There is no ONE database that works perfectly in e
by threeseed 14y ago
I just don't like the "right tool for the job" argument.
Then say the "right technology for the task" then.
There is no ONE database that works perfectly in every situation.
- jeffdavis 14y agoWhen installing a database system, it is rarely a "task". It's usually something that will live a long time and there will be many long-term consequences.
- rubinelli 14y agoBack in the day, many startups died with a gigantic Oracle database that cost them months of runway, because they had to "think long-term". Build for what you need now, and just make sure your "central repository of truth" isn't lossy. You can always replicate for specific use cases later.
- jeffdavis 14y agoI'm not saying that you shouldn't make short-term compromises. I'm saying that "right tool for the job" is sloppy reasoning. Even in the short term, it might be much faster to develop against a good RDBMS than a nosql system. I think many developers are so focused on "abstracting away the data store" that they forget what a good RDBMS can do for them.