2 ms·
Alright. So let's discuss how much time and effort it would take to build and maintain a Heroku replacement without k8s then. Besides, GP's criticisms were squ
by imiric 2y ago
Alright. So let's discuss how much time and effort it would take to build and maintain a Heroku replacement without k8s then.
Besides, GP's criticisms were squarely directed at k8s. For any non-trivial workloads, you will likely use operators and networking plugins. Any of these can have bugs, and will add complexity to the system. My point is that if you find any of those features valuable, then the overall cost would be much less than the alternatives.
- Maxion 2y agoThe alternative is not to build a different PaaS alternative, but to simply pay Heroku/AWS/Google/Indie PaaS providers and go back to making your core product.
- imiric 2y agoDid you read the reasons they moved away from Heroku to begin with? Clearly what you mention wasn't an option for them, and they consider this project a success.