3 ms·
Sure, I don't disagree. I've ditched sqlite for Postgres many times. It's just that for 99% of the projects I ever worked on, writes are like 100x less than re
by pdimitar 7y ago
Sure, I don't disagree. I've ditched sqlite for Postgres many times.
It's just that for 99% of the projects I ever worked on, writes are like 100x less than reads so wrapping the writes in a queue of sorts has been quite okay and performant.
It can and it has been coming to a point when it's easier to use a full-blown database server, too.
I was simply pointing out that for a lot of classic workflows wrapping/centralising writes works quite fine.