Welcome to another episode of the ThoughtWorks podcast. My name is Klaus. I'm a developer here in the Hamburg office of ThoughtWorks Germany.

And I'm joined today by Florian, who's also a developer at ThoughtWorks, Germany.

And he's the author of a two called Lambda CD, which we are going to talk about today.

Welcome, Florian.

Hi, thanks for inviting me.

So what is Lambda CD exactly?

Well, maybe it's best explained as it's the extension of the idea of infrastructure as code

between a build pipeline.

So normally you would probably set up your build pipeline by clicking around in your UI,

maybe in Jenkins or in GoCD.

I decided to try out what it would mean to do the same but completely in code.

So you can do all the power of your build pipeline,

all the power of your normal programming language to build your own build pipelines.

So how does that look like exactly? I know that by code you

mean closure and so it is it is a bit like a framework to to program a built pipeline. Right. That's

pretty much it. It's a closure library and there's also a nice template to get you started.

So in the end what you're doing, you're writing another piece of software.

But this particular piece of software is going to be the piece of software that runs your tests,

that you build your code, that deploys your code into any environment you like. So what you would do is you have a bit of boilerplate code to set up some of the basic sort of build pipeline,

and then you write a set of really small normal closure functions that would do what your build pipeline

steps would normally do.

And you assemble them in some structure that makes sense to you to define kind of the way your build pipelines should be assembled.

...