4 ms·
> 1. Is it really so complicated? Depends. Are you a >500 Developer org with many services? Then it's easy compared to what's out there. Anything less than tha
by harpratap 4y ago
> 1. Is it really so complicated?
Depends. Are you a >500 Developer org with many services? Then it's easy compared to what's out there. Anything less than that I'd say it's complex and you'd be better off using a PaaS
> 2. Is that complexity incidental or essential?
Depends. If you're going to do simple things forever then it's an overkill. But if you expect to grow in unknown ways in the future and don't want to waste your time doing bunch of migrations in the future then it's essential.
> 3. Could we get away with a simpler set of abstractions for 90% of applications?
Maybe? Heroku, AppEngine, CloudFoundry tried, but didn't go too far. Let's see what new crop of PaaS offerings are able to do
- threeseed 4y ago> Anything less than that I'd say it's complex and you'd be better off using a PaaS Kubernetes is available as a managed service in AWS, Azure, Google etc and this is likely to be the most popular deployment model. By any definition this is a PaaS and if you add in custom monitoring, logging, security, ingress etc. is going to be just as simple and significantly cheaper than using a managed solution. If you're just building a basic website then sure it's an overkill but fewer people are building those these days.
- throwawaycuriou 4y agoit really comes down to what you're building. many web app startups would be better served paying for PaaS that manage this for them. as an example: Netlify/Vercel. if you need a database add FaunaDB to that. if that sounds risky or expensive, consider the cost of building a DevOps team.