Hello, everyone and welcome to ThoughtWorks podcast.

My name is Jean-Mek, and I'm here today with my co-worker, Sheroy-Marker.

Welcome, Shoray.

Hi, J-Mark. Thanks for having me.

I'm Shari-Marker. I'm the head of technology for ThoughtWorks products. We build products that make software engineering teams more efficient.

Great. Great to have you. I'm super excited to have this conversation. It took us a while to

actually connect.

One of the products that your team builds is GoCity, which implements continuous delivery.

So I would like to pick your brain today about state of continuous delivery under the new, you know,

kind of microservices architecture,

under the containerized framework of deployment

and operating services and how that shifted

the developer experience.

So maybe we start with, you know, how continuously delivery worked before this architecture,

before modern distributed architecture.

So there's been a shift in architectural thinking while building large-scale applications off late.

So in the recent past, we were used to more larger monolithic systems

where a system could be comprised of smaller components.

So when you thought of continuous delivery in that context,

you would have to think about how these components depended on each other. And so if any of these components changed, what that

really meant for the system on the whole. So in that context, we used to see a lot of complex CD pipelines where a pipeline would consist

of a build of a smaller component.

...