3 ms·
You might be best served by some platform-as-a-service (Heroku, platform.sh, Netlify, ...) than by a cluster offering. PaaS are pretty much turnkey for many ap
by mgarstecki 4y ago
You might be best served by some platform-as-a-service (Heroku, platform.sh, Netlify, ...) than by a cluster offering.
PaaS are pretty much turnkey for many apps, and cost mostly scales with the actual usage which tends to fit well small companies.
They completely hide infra management from you, deployment can be entirely automated through Git with no SSH or Docker registry management, and they provide access to what you listed: config/secrets, logs.
- wernerb 4y agoThe interface/dsl should have to be really easy though to make it worth it. E.g., if you are making your own buildpack on heroku you have gone too far. The whole idea should be ubiquity in knowledge of these platforms. The idea that you can easily hire someone or expect someone to have these skills. Kubernetes might not be simple but it is becoming ubiquitous and that is worth something in the long run. So if you are looking for the easy solution, use a SaaS / PaaS that really is turnkey and, for example is not just another peaky abstraction of kubernetes. You are choosing an easy solution so you should not need to invest a lot of your energy. Likewise recognize that when you need more customization that you might need to jump ship instead of investing in ducktaping your SaaS/PaaS.
- wruza 4y agoI think we are already using paas (DO Apps) for a few services, but some requirements are incompatible with it and other paas’es. I’d like to rather have a thin layer over vps, what I do with ssh, but better UX.