The Services Your Microservices Could Be Like

Hello developers. Look at your microservices, now back to services, now back to yours, now back to services. Sadly, your microservices aren't actually services, but if they stopped following bad blogosphere advice, they could be.

We've all been there— working on a project that has grown large and difficult to work on. You're afraid to make any changes in one part of the system for fear that it will break at least 6 unrelated other parts. It takes you months to bring new team members up to speed on your project. You have deadlines coming up, but your system is so difficult to work on that you just have to accept that working nights and weekends is now the new normal. And then you read about microservices, the idea that you take parts of your big app and put them on a different server and speak to them over HTTP. And then it's all rainbows and unicorns again, right?

Right?

This talk starts by taking a critical look at the microservices trend, asking and answering important questions like: Does the term "microservice" actually mean anything? Does breaking an app apart make it simpler to work on? What actually is a service? Is the size of a code base what makes it a service or not? Do I need Kafka or RabbitMQ to have a service-based architecture?

It then proceeds with a path that actually *can* remove the coupling in your system, exploring architectural ideas like event sourcing and command query responsibility separation (CQRS). This talk is born out of real-world experience, and we'll actually build a small service-based system to illustrate the concepts and give you information you can put into action today.
[311]

Comments

Comments are closed.