Hello and welcome to ThoughtWorks podcast.

I'm Mike Mason.

I'm Jean-Marc de Jahnie.

I'm James Lewis.

I'm Suddarshan.

And today we're going to be talking about microservices.

In Sydney, Australia, putting together the new edition of the ThoughtWorks radar. And whilst kind of,

you know, doing the usual discussion and arguing about what should go on the radar and what we

should say about it, a number of things came up to do with microservices. And we thought we would

run a podcast on this. And especially since we have James in the room, James actually with Martin

Fowler authored one of the kind of original early articles defining what microservices really are.

So James, I thought maybe we could start with you giving us like a, you know, a brief history of how

microservices came about. Sure. So in order to be brief, we need to go back, maybe not quite as far as the beginning.

So if we start in 1969 with the birth of units, maybe not.

So I guess it was pretty around 2012 where I started seeing different organizations adopting, I guess, what we now

think of the microservice style. Fred George originally coined the term back around then

to describe a particular way of plugging together very, very small bits of functionality

generally attached to some form of message bus.

I guess at the same time you have organizations like Netflix in the US,

so they were talking about fine-grained service-oriented architectures.

That was Adrian Kotcroft's term for what they were doing at the time.

And then I think it was about 2012 where I attended a workshop called

...