3 ms·
It's a difficult one; if you don't know yet if you will have billions of transactions, you should focus on clarity and flexibility - that is, you should be able
by Cthulhu_ 3y ago
It's a difficult one; if you don't know yet if you will have billions of transactions, you should focus on clarity and flexibility - that is, you should be able to rewrite and re-architect your application and its runtime IF it turns out to be successful.
A parent comment mentioned SQL databases for example; those are great because they can scale both horizontally and vertically these days, sometimes with the click of a button in AWS.
Other good practices are things like stateless back-end services so they can scale horizontally, thoroughly documenting (and maintaining documentation) on business processes handled by the software, monitoring, etc.
Disclaimer: I'm an armchair expert, I've never had to deal with back-end scaling.
- coffeebeqn 3y agoSomething has gone horribly wrong if you don’t know if the requirements are 10 request per second or a billion per second. We build some services from the ground up for very high traffic and the hoops you have to jump through and the tradeoffs just don’t make sense for a basic CRUD thing which can run on a boring ole machine and a little SQL instance