News for hackers. Stuff that matters.
Re:Maybe You Don't Need Kubernetes by lazyjones on Saturday March 23, 2019 @08:13AM (#19470113)
> Heroku turns a strategical liability ("I have only one employee who understands what rsync is; if he leaves I'm screwed") into a fiscal one

So, what's your plan in case Heroku shuts down, or gets bought and changed completely? Isn't that also a strategic liability, just a much larger and arguably less likely one?

Re:Maybe You Don't Need Kubernetes by jacques_chester on Saturday March 23, 2019 @10:06AM (#19470493)
Heroku got bought by Salesforce several years ago.

If you have 12-factor apps then you have a fighting chance of moving off it anyway.

Apart from Dokku, I'd say Cloud Foundry is the closest next environment that you can install and operate directly, though it's an 800-pound gorilla by design. But there are fully hosted services for it (eg. Pivotal Web Services, IBM BlueMix, SwissCom Application Cloud). There're also semi-hosted options (Rackspace Managed Cloud Foundry) and IaaS-provided installer kits for AWS, Azure and I think GCP as well. You can also buy commercial distributions from Pivotal, IBM, Atos, SUSE, IBM and SAP.

Disclosure: I work for Pivotal, we sell Cloud Foundry and Kubernetes distributions (PAS and PKS).

Re:Maybe You Don't Need Kubernetes by user5994461 on Saturday March 23, 2019 @08:45AM (#19470217)
It's a negligible liability compared to the risk of the devops guy leaving the company within a year, without leaving any documentation or any clue how the app was deployed or run. The same thing will happen next year with the replacement guy, if there ever is a replacement.
Re:Maybe You Don't Need Kubernetes by ngrilly on Saturday March 23, 2019 @10:04AM (#19470483)
Use Google App Engine, Clever Cloud or Scalingo.