O'Reilly: Microservices Need Architects

Help guide your organization in the areas of service design, system design and even organizational design

Much of the public discussion on Microservices is coming from software developers who feel liberated by the chance to code without the constraints and dependencies of a monolithic application structure. While this perspective is important and compelling for the developer community, there are a number of other important areas of Microservice architecture that aren't getting enough attention. This O'Reilly article by Matt McLarty of the API Academy discusses how architects can help guide their organizations in the areas of service design, system design and even organizational design.

The Author

Matt McLarty

Team Lead

Matt McLarty is an experienced software architect who leads the API Academy at CA Technologies. He helps organizations with their strategy and architecture for APIs, microservices and enterprise integration. Matt recently co-authored the book Microservice Architecture for O’Reilly, with his API Academy colleagues.

Related Articles

Microservices

Voltaire, Vonnegut, and the Vocabulary of Microservices

The lack of common concepts and axioms is holding the software engineering industry back. This blog post explores the need for a common distributed systems vocabulary to help with that problem.

Matt McLarty on Aug 10, 2018

Microservices

Applying and Extending DHARMA

This post gives some practical examples of the DHARMA method for API Security in a Microservice Architecture, and also shares some opportunities for extending the model.

Matt McLarty on Jul 9, 2018

Microservices and APIs
API Strategy

Microservices, APIs and Innovation: The Power of APIs

Explore the role APIs play in empowering teams and enabling organizations to innovate.

Mike Amundsen on May 24, 2018

Join the Conversation