December 26, 2019

215 words 2 mins read

Microservice standardization

Microservice standardization

Microservice architecture brings freedom for developers, but building a sustainable microservice ecosystem requires holding microservices to high architectural and operational standards. Susan Fowler introduces a set of standards that apply to all microservicesstandards that ensure microservice availability while preserving developer freedom.

Talk Title Microservice standardization
Speakers
Conference O’Reilly Software Architecture Conference
Conf Tag Engineering the Future of Software
Location San Francisco, California
Date November 14-16, 2016
URL Talk Page
Slides Talk Slides
Video

The adoption of microservice architecture brings a considerable amount of freedom to developers—freedom to make their own decisions about language, architecture, development tools, and the like. While this romantic idealization of microservice architecture is true in principle, not all microservices are created equal, nor should they be. To build a sustainable microservice ecosystem, one in which microservices interact with one another seamlessly, we need to hold our microservices to a set of very high architectural standards. Susan Fowler introduces seven principles of microservice standardization that are general enough to apply to every microservice at every company yet specific enough to be quantifiable and produce measurable results: every microservice must be stable, reliable, scalable, fault tolerant, performant, monitored, and documented. Susan dives into the requirements associated with each standard and shows how they work together to produce highly available and sustainable microservice ecosystems.

comments powered by Disqus