3 ms·

Marketing speak aside, I'm curious what is actually changing for the end developer in the "next generation". Heroku already supports building and deploying cont

• schneems 2y ago
  One big part that I'm personally excited about is support for Cloud Native Buildpacks. It's an open spec, part of the CNCF, and produces container images. You can use it to debug locally and can try it out now https://github.com/heroku/buildpacks/blob/main/docs/ruby/README.md https://github.com/heroku/buildpacks/blob/main/docs/ruby/REA.... To go along with that we've built and maintain a Rust framework for writing CNBs https://github.com/heroku/libcnb.rs https://github.com/heroku/libcnb.rs. I maintain the Ruby CNB and so I'm pretty excited to see some of my stuff in action. > Heroku already supports building and deploying containers Kinda. Heroku created a container ecosystem before OCI images were a thing. Apps deployed to the current Cedar infrastructure are deployed as "slugs" basically a tgz of the application directory that's loaded onto an LXC container, and unzipped to run on a base image (also called a stack) https://devcenter.heroku.com/articles/slug-compiler https://devcenter.heroku.com/articles/slug-compiler. One big benefit of moving towards a standards compliant future instead of homebrew, is that customers also have access to that ecosystem. That's what enables things like being able to run and debug application images locally. It's the standards and community. We went fast and blazed some trails, now we're aiming to "go far," together with the community.