4 ms·
> 20-100 transactions per second In all seriousness, that is "no load". I know it fits 99% of all startups, and many larger companies too, but that's kind of t
by groestl 2y ago
> 20-100 transactions per second
In all seriousness, that is "no load". I know it fits 99% of all startups, and many larger companies too, but that's kind of the point.
I wouldn't do it differently though, I think it's a perfectly fine architecture :)
- t-writescode 2y ago> > 20-100 transactions per second > "no load" Ruby on Rails applications with even a modest amount of ActiveRecord work would like a word xD
- sethammons 2y agoCouple thousand per second is expected on my Go services (per node) before any optimizations.
- marcosdumay 2y agoIf so, you may want to rent more than one server and set multiple web servers with a centralized database. Like people did in the 90s! But that will cost more than $10/month.
- raxxorraxor 2y agoDepends on the service. For b2b that is already a lot.
- marcosdumay 2y agoThat's huge supermarket inventory system top load. Or rather, the lower end of that is huge supermarket inventory system top load.