MicroServices For Better And Worse (with Ian Cooper and James Lewis)
About this episode
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.
–
Residuality Theory: https://leanpub.com/residuality
Support Developer Voices on Patreon: https://patreon.com/DeveloperVoices
Support Developer Voices on YouTube: https://www.youtube.com/@developervoices/join
Ian on Mastodon: https://mastodon.social/@[email protected]
James on BlueSky: https://bsky.app/profile/boicy.bsky.social
Kris on Mastodon: http://mastodon.social/@krisajenkins
Kris on BlueSky: https://bsky.app/profile/krisajenkins.bsky.social
Kris on LinkedIn: https://www.linkedin.com/in/krisjenkins/
Kris on Twitter: https://twitter.com/krisajenkins
Get every episode summarized
Each time Developer Voices publishes, we email you a written briefing from the transcript — the topics, who appeared, and any specific claims, with the ad reads skipped.
Email me new episodesFree for 3 shows. No card needed.
Hosts & guests
No transcript yet
This episode has not been transcribed. Request it and it moves to the front of the queue.
More episodes
More from Developer Voices
DuckDB And The Burden of Success (with Hannes Mühleisen)
Developer Voices
The Enterprise AI Gap (with James Brown)
Developer Voices
What If Every SQL Query Could Update Incrementally? (with Lalith Suresh)
Developer Voices
What's Worth Knowing In AI Right Now? (with Henry Garner)
Developer Voices