Buildpacks and Paketo with Ram Iyengar

This page summarizes the projects mentioned and recommended in the original post on dev.to

Our great sponsors
  • Scout APM - A developer's best friend. Try free for 14-days
  • Nanos - Run Linux Software Faster and Safer than Linux with Unikernels
  • SaaSHub - Software Alternatives and Reviews
  • GitHub repo PostgreSQL

    Mirror of the official PostgreSQL GIT repository. Note that this is just a *mirror* - we don't work with pull requests on github. To contribute, please see https://wiki.postgresql.org/wiki/Submitting_a_Patch

    Aaron: And everybody is always telling me I should just be using containers. I don't need to run Postgres locally on my machine, and I could just have it in the container. But I do very well in keeping my Python environments separate. I do use virtual environments there. But yeah, I guess being a developer advocate, you probably come across it yourself as well. We're very often working on a team of one on a project. [laughs] So it's very easy to skip through best practices. So anything that can make it easier for me to have a nice local dev environment, I'm all for it. So as well as the Buildpacks then, tell me a little bit more about your work at Cloud Foundry. So you're not just like a Buildpack advocate. You're an advocate for Cloud Foundry itself. Is that correct?

  • GitHub repo Cloud Foundry

    Deprecated: Cloud Foundry Release

    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.

  • Scout APM

    Scout APM: A developer's best friend. Try free for 14-days. Scout APM uses tracing logic that ties bottlenecks to source code so you know the exact line of code causing performance issues and can get back to building a great product faster.

  • GitHub repo kubernetes

    Production-Grade Container Scheduling and Management

    So just to sort of go tangential here for a bit, Cloud Foundry defines developer experience that mimics the Heroku one, so like we had Git push Heroku master or something like that. Cloud Foundry makes use of cf push. And as long as you provide the path to the source code, the Cf push command itself is aware about what language your source code is in and what needs to be the build process. And the output was a binary that was deployed to a virtual machine back in the day. So the popularity of that was quite huge, so a lot of enterprise-grade users as well as a lot of medium teams, a lot of small teams. So Cloud Foundry has a pretty big user base as a PaaS. And the same experience was translated to a Kubernetes cluster. And this was about a little over a year ago. They made the first announcement. So the project is CF For K8 so which is again the same sort of convenient developer-friendly past experience. But only now it will export a container image instead of a binary, and it will deploy to a Kubernetes cluster instead of a bunch of VMs.

  • GitHub repo pack

    CLI for building apps using Cloud Native Buildpacks

    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.

NOTE: The number of mentions on this list indicates mentions on common posts plus user suggested alternatives. Hence, a higher number means a more popular project.

Suggest a related project

Related posts