Re:One million queries per second with MySQL
by prescriptivist on Thursday September 01, 2022 @09:52PM
(#32685691)
No one is running their OLTP and batch processing workloads on sqlite (bedrock or not) at scale. There may be unique cases for specific situations but show me an org with large and broad concurrency demands running sqlite at scale and I'm happy to be proven wrong.
[ Parent
| on HN ]
Re:One million queries per second with MySQL
by hansvm on Thursday September 01, 2022 @09:56PM
(#32685720)
That sounds like a leadership problem rather than an indictment of sqlite
Re:One million queries per second with MySQL
by prescriptivist on Thursday September 01, 2022 @10:05PM
(#32685770)
No, it's pretty much an sqlite problem. As good as it is for limited concurrency situations (and synthetic benchmarks like this expensify blog), it does not compare to mysql or postgres for mediating hundreds or thousands of transactions per second.
Re:One million queries per second with MySQL
by blowski on Friday September 02, 2022 @01:24AM
(#32686911)
One of the current Hacker News shibboleths:
If SQLite is not the solution, change the problem.
Re:One million queries per second with MySQL
by rawoke083600 on Friday September 02, 2022 @03:32AM
(#32687734)
Haha too true !
If I may add:
World: "We solved Cold Fusion !"
HN: "Meh"
World: "We solved Cold Fusion in RUST !"
HN: "Shuttup you demi-god of tech and take my upvote !"
Re:One million queries per second with MySQL
by hansvm on Friday September 02, 2022 @02:00AM
(#32687117)
Maybe, maybe not, but that wasn't the claim here. It was just a shitty argument against sqlite, one that could equally apply to mysql, lisp, questdb, apl, and a host of other tech if it were valid. Organizations choose tech stacks for a ton of reasons, most of which are only loosely related to performance and maintenance characteristics. The (proposed) fact that most organizations don't scale out sqlite doesn't say much at all about whether doing so I'd a good idea.