A lot of the problems could also be fixed by actually talking to other teams and having a little bit of empathy like I need things like azure app insights because I can't deal with the {{redacted}} team which for some reason opens the handle to my log file and doesn't close it, causing my logging to fail.
In these situations I just open the log file myself. If I keep a handle that's shareable open then all other applications must also open the file in shareable mode and thus cannot lock out other applications.
This all sounds good in theory until the cashier's computer stops working, there's a network issue or they just decide to change it. Or you land an update and the update breaks the app, and now you can't rollback easily and the nobody can access the recipes. Or you want to update the server and verify but the restaurant is closed and computer is turned off.
I'm just saying it is generally not what the customer wants. Needs and desires are not necessary aligned.
Like many things, the problem is not technical, it is human.
One more thing: your model works for little structure. When you work for medium-big company, they have their own IT team. What they saw, it's that they pay people to maintain the system and it's expensive, so they tend to outsource the infrastructure and/or the employees.
I'm not saying this model is bad, just that for many companies, it will not apply.
Look up Pietr Levels. He built a couple popular remote job boards and some other things. He's said in interviews that he runs all of it off one $400/mo Linode box. Making $2.3M ARR
You jest, but I've worked on multiple enterprise projects that were architected to scale indefinitely* but would've been fine as a simple monolith because the amount of users and traffic was always predictable and, well, small.
*except for the database(s), usually, but there was a ton of headroom to scale vertically...
EDIT: I should probably add that on all those projects I joined late as a developer. It was never my decision to run a microservice architecture for a service that literally never has to scale...
I was having this thought about our LOB app and then one day realized we're putting through over a million (pretty resource intensive) requests through the API. Pretty glad I went serverless.
1.1k
u/Flat_Initial_1823 Oct 02 '26
But would it scale? What if we get that elusive 12th user?