By Pulumi recently introduced Pulumi Registry, a searchable collection of Pulumi Packages published by Pulumi and partners. “Pulumi Registry is a place to find packages; it gives users access to building blocks across 60-plus cloud providers including but not limited to AWS, Azure, GCP, Kubernetes and so on,” said Joe Duffy, CEO of Pulumi. In this episode of To The Point, Duffy explains what is Pulumi Registry and how users can leverage it.
Guest: Joe Duffy (LinkedIn, Twitter)
Company: Pulumi (Twitter)
Show: To The Point
Swapnil Bhartiya: Going back to Pulumi, and you earlier mentioned Pulumi registry. You briefly touched upon that, but I want to go a bit deeper into that. Explain a bit, you know, what it is, why you folks came out with it, and how people can consumer use it.
Joe Duffy: Yeah, absolutely. You know, in Pulumi, it’s an infrastructure’s code technology, we, but different from a lot of other tech, you know, we didn’t do YAML or domain-specific language. We said, hey, let’s use general purpose languages like Python, JavaScript, Go, et cetera.
So you can use the language you’re familiar with, get powerful tools in IDEs, and great programming constructs. And one of the things you get is sharing and reuse. You know, standing on the shoulders of giants of programming languages, the way we’ve tamed complexity in a bunch of different domains, is abstraction, modularity, sharing and reuse, building bigger things out of smaller things.
And what excited us with Pulumi is now with infrastructures code, in general purpose languages, you can apply that to infrastructure. So you’re not always copy and pasting YAML all over the place, relearning the same mistakes, making the same security mistakes, time and time again. You can benefit from real sharing and reuse.
So the registry is a place ago to find packages that you can basically get access to building blocks across, you know, 60 plus cloud providers. AWS, Azure, GCP, Kubernetes, a lot of great things, but also go from building blocks to architectures. So if you want to do like a full EKS cluster, that’s fully configured with Prometheus, and you’ve got an off-the-shelf component that you can use and don’t need to be an expert in literally everything about that hard problem.
And this is what I was alluding to earlier. I think the next phase is, hey, let’s stop all of us doing the same grunge work that is undifferentiated and easy to get wrong, and frankly, no fun. And let’s move to building bigger things out of smaller things. And really that’s that’s the way I think we take the whole cloud space to the next level.
