How to Decide What Microservices to Build, and What Messages They Should Send - ERP Spain.com - España y América Latina

The microservice architecture has become an established and powerful way to structure large scale systems, providing a component model that scales both at the human and system levels. It is by nature an architecture that has lots of small parts. And it's easy to make a big mess with lots of little things. Complexity has moved into the network. That's a better place for it than unreadable code. But you still need to know how to manage that complexity. What are the patterns that you use to build message flows between services? What are the ways that those messages flows will fail? Are they scalable? How do you distribute complexity evenly? To answer these questions, you need to be able to visualize your microservice interactions, so you can describe them and make them accessible. This talk provides practical answers to those questions, provides you with a method for designing microservice architectures, and introduces a new visual syntax to describe them. Speaker's bio: Richard Rodger is a co-founder of nearForm.com. Richard is an expert and thought-leader in next-generation enterprise software delivery, with a focus on Node.js and microservices. He is currently writing The Tao of Microservices (available on early release from manning.com/books/the-tao-of-microservices), a comprehensive guide to designing and building microservice systems. His first book Mobile Application Development in the Cloud (Wiley, 2010) is one of the first major works on the intersection of Node.js, Cloud, and Mobile. Richard was previously CTO of FeedHenry, a mobile application platform provider that was acquired by RedHat for €63.5m in 2014. Since Richard co-founded nearForm in 2011, the company has become the world’s largest Node.js and microservices consulting company.