I want to share my slides and a summary of my talk “Move fast and s/break/make things (microservices are topologies of business logic) at the O’Reilly Software Architecture Conference in New York in April 2017.
Microservices have been around for about 5 years now, and at this point it is widely accepted as a best practice. Despite this, microservices are still very poorly understood– lots of companies are struggling to adopt microservices and even those that “successfully” adopt microservices aren’t seeing all the benefits they expected.
This is because we are a very tech-centric industry and as a result we tend to look at microservices through a highly technical lens. The reality is that most of the benefits that microservices can provide come from the organizational and process changes that occur as a result of the change in tech. Without understanding these changes, it’s difficult to successfully apply any of the tooling. The good news is, there are relatively few basic principles at work that can serve as a map to help guide you through all of the tooling and apply it effectively.
This talk looks at microservices from three perspectives: first the process, then the people, and finally the technology. We’ll talk about development practices that let you produce large networks of services in a robust configuration really quickly, the impact when you throw more people at your problem, and the technology you need to support all of this.