There is no reason it has to be that hard to have the scalable infra out of the box. There should be some setup out there, ideally portable, where setup is one command and now I have a working scalable demo app (multi-user todo, fb clone, instagram clone, etc...)
That setup should include unit tests, integration tests, a/b deployment, rolling upgrades, versioning, local dev, staging servers, production servers, data backups, logging infra, etc...
The inputs to get started should be as simple 10 questions. Domain names, service names, ...
As is now, setting up a new scalable website is similar in some ways to trying to setup a new computer if linux, macos, windows didn't exist and you had to write your own OS from existing parts. There's no reason it should be this way. There's a set a reasonable defaults that would work for most projects.
I wouldn't consider that too complex or over engineered. I'd consider it simplified the same way the fact get I get so much from existing OSes simplifies using my computers vs having to write my own OS for every new computer I buy
That setup should include unit tests, integration tests, a/b deployment, rolling upgrades, versioning, local dev, staging servers, production servers, data backups, logging infra, etc...
The inputs to get started should be as simple 10 questions. Domain names, service names, ...
As is now, setting up a new scalable website is similar in some ways to trying to setup a new computer if linux, macos, windows didn't exist and you had to write your own OS from existing parts. There's no reason it should be this way. There's a set a reasonable defaults that would work for most projects.
I wouldn't consider that too complex or over engineered. I'd consider it simplified the same way the fact get I get so much from existing OSes simplifies using my computers vs having to write my own OS for every new computer I buy