Cloud Foundry VS Nomad

Ram: Yeah. I'm glad you asked that question because, like I mentioned, there are like two peaks to the Buildpacks adoption sort of curve. In the first version or first avatar of Buildpacks, they weren't very agile in terms of the platform, the end platform that they would deploy to. So Heroku started off with this. I think they open-sourced a lot of the internals. And then Cloud Foundry, which was Pivotal back in the day, had their own version of Buildpacks with their own version of the life cycle and everything. And so, it was very distinct in terms of what the target platform was for the Buildpacks to go out and make a deployment. Between the first and the second sort of peaks, Docker, or rather the popularity of containers, really took off. So Docker happened. I am just using Docker and containers very interchangeably, so; please forgive me for that.

Cloud Foundry is an open-source tool for writing code in any language, with any framework, on any Kubernetes cluster. Provides a highly secure environment in which you can bypass complex configuration and routine operational tasks. Integrates with your environment and tools, including CI/CD and IDEs. Security patches are implemented quickly in response to vulnerabilities, so it stays secure for sensitive, mission-critical application development.

You'll probably want to take https://www.nomadproject.io/ and layer it on top of jails with pot:

Nomad[1] is one alternative that gives you the same infra-as-code warm and fuzzies but isn't a behemoth like k8s. It's simple to deploy, simple to operate and unless you're truly scaling big, it probably does everything you need.

I'm sure there are others in the same league that I don't know about. Maybe I'm just getting old but I'll never understand the rush to use k8s in teams of <100 developers.

[1] https://www.nomadproject.io/

Hashicorp Nomad? I ran it across a bunch of raspberry pis and proxmox VMs/LXCs. Being a Hashicorp product it plays well with Terraform. The only reason I swapped it out for k3s was upskilling for work.

[Nomad]

Lob’s core API has been fully migrated to HashiCorp's Nomad, Lob’s Next Generation service platform. This is a major milestone for the Nomad Project, the Platform Team, and Lob Engineering. This migration is the culmination of a year of R&D, months of practice migrating other Lob services, and weeks of work on this particular service. It’s absolutely worth celebrating for the complexity and customer impact.

Most of our API’s migration to Nomad happened in August, but the key feature of autoscaling was not working as expected. This turned out to be a bug in Nomad which James Douglas tracked down. The issue was recently fixed and autoscaling works as expected, completing the migration!

Nomad by HashiCorp

There's also https://pot.pizzamig.dev/ which even has a Nomad(https://www.nomadproject.io/) driver in case you want to "orchestrate" the jails(as in deploy many jails at the same time across multiple servers)

The check stanza runs a health check on the service Since the service is registered to Consul, the health check runs on Consul. The above health check is configured to run every 10 seconds, and is given 5 seconds for the health check query to succeed. Health checks in Nomad are similar to Kubernetes health checks.

Not sure if it fits here, and might be a little more complex than what you’re looking for, but Nomad is definitely worth a look.