3 ms·
While I agree with you as a matter of an ideal, the step from one database to two is infinitely larger than from two to more. Given budget, time and engineering
by Etheryte 2y ago
While I agree with you as a matter of an ideal, the step from one database to two is infinitely larger than from two to more. Given budget, time and engineering constraints, sticking everything in one database is by far the sanest solution for the vast majority of code out there.
- hinkley 2y agoI think microservices kind of break that wall with a herd of stampeding elephants being chased by even angrier bees. If you're still using one database in 2025, even if you wouldn't touch microservices with a ten foot pole, then you've got some problems. OLAP, KV, cache heirarchies, you aren't running a singular database, except maybe for a standalone app.