4 ms·
> No benchmark = no download. Perhaps it's because I'm particularly snarky pre-morning coffee, but this doesn't come across as the welcoming attitude open sour
by runlaszlorun 3y ago
> No benchmark = no download.
Perhaps it's because I'm particularly snarky pre-morning coffee, but this doesn't come across as the welcoming attitude open source is supposed to be and comes across as downright entitled. Especially as the first thing to lead with. Maybe you didn't quite mean it that way?
I'm taking a wild guess to say that you don't have a screaming need to run 'SELECT * FROM user LIMIT 1;' tens of thousands of times per second on SQLite.
And if you did, I'm guessing you prob would be able to write your own API in front of it.
Am I wrong here?
Kudos to the authors of this tool. It looks great and I'd love to try it out on a recent project.
- geenat 3y agoWho really wants to build on top of something just to hit an immediate performance cliff? How far you can vertically scale on one server before requiring a split or shard in your data is why it's a big deal. A) App servers are easy to scale (stateless, add hardware). B) Database servers are hard to scale (requires changing logic). If you're immediately hitting B) you're probably screwed.