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/@ICooper@hachyderm.io

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

MicroServices For Better And Worse (with Ian Cooper and James Lewis) 47:09 Share

Developer Voices

Shownotes Transcript

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