Ringo De Smet
Ringo started his career as a software engineer in C++ and Java in the late '90-s. Over the years, he evolved from software engineering, over release engineering to operations and back.
Ringo currently works as a Customer Experience Architect at Pulumi.
Sessions
On a regular basis, articles and tweets pass by discussing whether some specific tool is imperative or declarative. It’s no surprise that Pulumi is often the tool being debated.
This talk will explain why the right combination of imperative and declarative implementation aspects on your tool(s) deliver the power you need to solve your problems.
Ringo will analyse the following tools and pinpoint which parts of them are imperative and declarative:
- an older tool (Chef)
- two current tools (Pulumi, Helm)
- a recent one from another domain (Dagger)
To wrap up, Ringo will reason why the introduction of imperative programming languages in our tooling solves our most pressing need: integration!
In a world where the boundary between applications and infrastructure becomes thinner by the day, how do you link your application services to infrastructure provisioning?
In this workshop, we will simulate the case of a service provider who needs to set up a tenant when a new customer signs up. We will use the Pulumi Automation API to embed Pulumi as part of the solution.
Every participant can tailor the workshop in such a way it applies to their own company (or employer).
How can you provide a self-service model to infrastructure for your developers, but still have all the operational and security concerns fulfilled? Pulumi Packages to the rescue!
Developers can work together with operations and security people to build out infrastructure components which have all the functional and non-functional requirements integrated. As they are software components, these can be put under source control, unit tested and properly versioned.
Not all teams in a company use or prefer the same language. Pulumi Packages allow for components to be implemented in a single language but still consumed from any of the programming languages supported by Pulumi.
Ringo will shortly explain Pulumi’s architecture, so everyone understands the process. We then start to build the components, create all the SDKs for the Pulumi supported languages and consume at least one component from another language to see all the pieces at work.