3 ms·
Because developers without significant database / data store experience are choosing where to put their data because its "easy to use". Yes, RBDMS and similar
by bsg75 14y ago
Because developers without significant database / data store experience are choosing where to put their data because its "easy to use".
Yes, RBDMS and similar approaches are difficult to work with [1] and introduce "impedance mismatch". Yes joins can be slow. Yes scaling can be difficult and or expensive. But, when choosing where to put data without understanding (or accepting) why the above is difficult is only asking history to repeat itself.
[1] "Database guy here". I know databases and SQL. I would not consider choosing what language to implement a web application tier on, because I don't have enough relevant experience. I focus on what I have battle experience in.
- ig1 14y ago"Easy to use" is a perfectly legitimate criteria to optimize for. For most startups performance/scale is a total non-issue, most of the time even something like berkleydb would do. At most early stage startups developer time is the single biggest bottleneck. If you make a non-optimal choice upfront you can always migrate to another database later on (database migrations are painful but in practice is something you have to do sooner or later in any case). (obviously this applies to the scaling argument; if you need transactions you should pick a database which supports them)