Microservice communication
Architecture is all about the boxes and arrows. Whilst the boxes themselves can be interesting, it’s the arrows between them that this class will focus on. How can microservices communicate with each other?
No two classes are the same, with the attendees driving the exact agenda, but expect to cover the nature of synchronous and asynchronous communication, request-response vs event-driven collaboration, and why friends don’t let friends use distributed transactions. Along the way we can talk about the merits of different types of message brokers, why Sam now thinks schemas are cool again, and how event sourcing can be incredibly confusing.
Please note, this is not a coding class, but it is highly interactive. There will be lots of discussion - computing is all about trade offs, and this is especially true in the space of microservice communication. There is no one perfect solution, but by the end of the class you’ll better understand what trade offs might be important to you.
Sam Newman is interested in technology at the intersection of things, from development, to ops, to security, usability and organisations. After over a decade at ThoughtWorks he is now an independent consultant. Sam is the author of "Building Microservices" from O'Reilly. He has worked with a variety of companies in multiple domains around the world, often with one foot in the developer world, and another in the IT operations space. If you asked him what he does, he’d say ‘I work with people to build better software systems’. He has written articles, presented at conferences, and sporadically commits to open source projects. While Java used to be his bread and butter, he also spends time with Ruby, Python, Javascript, and Clojure, Infrastructure Automation and Cloud systems.