MicroServices For Better And Worse (with Ian Cooper and James Lewis)

What have we learned from more than a decade of deploying microservices? Was it a good idea? Are we any better at figuring out what a microservice is, or where its boundaries lie? Does splitting things up create fragmentation problems? And is it too late to put the genie back in the bottle? This week we’re going to look at all these questions and more as we reflect on the lessons learnt from this big architectural idea.

This interview was recorded live at GOTO Copenhagen, with two microservice experts and thinkers: James Lewis of Thoughtworks and Ian Cooper of JustEat.

–

–

0:00 Intro
2:52 Were MicroServices A Good Idea?
6:38 Defining Boundaries Between Services
13:42 The Dependency Inflexion Point
18:17 Are MicroServices A Tech Solution Or A Social One?
29:49 Simulations All The Way Down
32:43 Cross-Cutting Concerns
41:36 Applying Techiques In Context
45:10 Outro

[LukasRotermund]

Some more options for 2:00 (just for the algorithm 😉)
- does services define services?
- does teams define teams?
- does services define architects?
- does teams defines architects?
- does architects define teams?

[egnqqtc]

Really love your approach to Dev. content. Big fan.

[Endelin]

Interview request, the author of Raylib. Thanks for the great interviews.

[avwie]

Very good questions asked by you about the reason of data mesh and they answered it with anecdotal evidence basically boiling down to “this and this company implemented a db wrong and that’s the reason relational DBs don’t scale”

I was not impressed with the guests answers .

[luinnar]

We are taking circles in IT all the time. Ideas about simulating software/putting designs into stresses before creating it, looks very similar to Margaret Hamilton's Development Before The Fact

[evarlast]

I didn't hear Conway's law mentioned. Microservices are a result of Conway's law. err... I guess 19:20 the definition is said. We should give it a name. The name is Conway's law.

[octaviomontt]

Thank you so much for this!! As a 4-year-old developer, this kind of pannels really help me to orientate with a more critical thinking approach under all the noice that is in tech right now. It is hard to find wisdom in such a young profession and I think this content is exactly that. Thank you for all the amazing content ❤

[chrismettler]

I have used DCOM, CORBA, J2EE, RMI, SOAP and so on. At the end single responsibility principle is what counts no matter what tech/architecture you choose.

[MrHopp]

There is miles of difference between run of the mill programmers and software engineers who can reason about data and systems at scale. Everything changes at scale.

[JLarky]

Enjoyed listening to this for 47 minutes and not learning anything

[vncstudio]

Good discussion. Microservices are fine. It's about boundaries and level of granularity.

[alst]

“Quantity has a quality of its own” unknown, often attributed to Stalin

[aragroth]

What is the name of the book they mentioned at the end? It's not well audible