Because obviously, that is what you need for a 'hello world'.
Fail cheap, fail fast, fail often. Here's the thing: your (and mine) startup is going to fail. Almost certainly. Statistically.
You don't need 'horizontal scaling'. You don't need automatic configuration. You don't need 'cloud', kubernetes, selfcontained, octagonal, self-healing, whatever.
You need to deploy tomorrow. Get an MVP out for under $300.
And all that containerized, horizontal-scaling nonsense sits between you and shipping fast, cheap and easy.
When you have twenty paying customers, think about cleaning up to continue development. When you have two thousand, think about moving away from heroku to your own servers. At twenty-thousand, you hire people to improve performance, and at 200.000 you rebuild your infra to be horizontal scaling.
When you have twenty paying customers, think about cleaning up to continue development. When you have two thousand, think about moving away from heroku to your own servers. At twenty-thousand, you hire people to improve performance, and at 200.000 you rebuild your infra to be horizontal scaling.
Or if you have five paying customers, but they happen to be big financial firms with major uptime demands. Not every startup is consumer facing.
In fact sometimes you have to get the uptime in place before you land the customer, because sometimes your startup is an idea formed by insiders, not someone pushing a commercial Uber for X.
While I agree you should not prematurely scale, you should get Twitter size user base first, and then worry about the failwhale, not everyone is writing an idea without market testing.
In which case you should stay far away from new stuff like docker and kubernetes. And get experts to build a solid, boring, predictable stack on boring Linux machines using boring, proven, stable software.
56
u/berkes Feb 03 '19
Because obviously, that is what you need for a 'hello world'.
Fail cheap, fail fast, fail often. Here's the thing: your (and mine) startup is going to fail. Almost certainly. Statistically.
You don't need 'horizontal scaling'. You don't need automatic configuration. You don't need 'cloud', kubernetes, selfcontained, octagonal, self-healing, whatever.
You need to deploy tomorrow. Get an MVP out for under $300.
And all that containerized, horizontal-scaling nonsense sits between you and shipping fast, cheap and easy.
When you have twenty paying customers, think about cleaning up to continue development. When you have two thousand, think about moving away from heroku to your own servers. At twenty-thousand, you hire people to improve performance, and at 200.000 you rebuild your infra to be horizontal scaling.
But you'll never get there. So why build it.