5 ms·
The problem I have with this approach is that I don't know from the start what my needs are. For example if I'm building a web app in my free time ... I'm star
by bad_user 16y ago
The problem I have with this approach is that I don't know from the start what my needs are.
For example if I'm building a web app in my free time ... I'm starting with Mysql, and an ORM client like Django's, and I'm doing data-modelling that fits these tools.
Then if I would want to switch to MongoDB, if the need arises, I end up throwing away a lot of code / rewriting lots of logic. This means waisted hours and my free time for working on such stuff is very limited.
In lots of scenarios it's easier for me to just do sharding where I need it on top of MySql.
And that's what RDBMSs are good for ... they come with lots of crap you don't need, but that you may eventually which makes them fit most problems, unless you have extreme scalability needs, and even then you've got workarounds to turn to.
How do you know if / where you'll have scalability problems? And how do you know what to choose when you're doing exploratory programming?
- mbreese 16y agoHow do you know if / where you'll have scalability problems You won't. Just code it for the best model for your data. 95% of the time a RDBMS will work just fine for your data. If you have scaling issues down the road, chances are you'll be working on this full-time and will have the energy to devote to properly thinking about scaling. You aren't Google or Facebook (yet). Until you are, just work with what best fits your data or is fastest to code.