Gartner Research

How to Succeed With Microservices Architecture Using DevOps Practices

Published: 22 January 2019

ID: G00360897

Analyst(s): Gary Olliffe, Kevin Matheny

Summary

Microservices architecture helps deliver agile, scalable software, but success requires more than new architecture patterns. Technical professionals responsible for application architecture must lead changes to processes, organization, platforms and data management to deliver business impact.

Table Of Contents

Problem Statement

The Gartner Approach

The Guidance Framework

  • Prework
    • Recognizing Complexity
    • Understanding Your Business’s Demand for Change and Willingness to Invest in MSA
  • Part 1: Improving Your Processes
    • Mature Your Agile Development and Deployment Processes
    • Meet Demand for Rapid, Continuous Delivery With a Fluid Release Schedule
    • Optimize Your Testing and Quality Assurance Processes
    • Address New Governance Needs
  • Part 2: Organizing People and Building Skills
    • Embrace the Organizational Structure Needed to Deliver Microservices
    • Champion Required Cultural Behaviors
    • Build the Required New Skills and Capabilities
  • Part 3: Building the Technology Platform
    • Preparing the Technical Architecture Needed for Microservices
    • Choosing Hosting Targets and Units of Deployment
    • Selecting Tools in a Crowded and Evolving Microservices Technology Market
  • Part 4: Defining Your Services
    • Be Pragmatic About the Microservices Principles
    • Be Iterative About Service Decomposition
    • Apply Domain-Driven Design and Bounded Context to Scope Your Microservices
    • Define Evolvable, Versioned Interface Contracts
    • Decouple Your Published APIs From Your Microservices Implementations
  • Part 5: Decoupling Your Data
    • Make Architectural Trade-Offs to Balance Complexity and Agility
    • Model Your Data Relationships Based on API Contracts
  • Follow-Up

Risks and Pitfalls

  • Pitfall: Being Too Dogmatic in Pursuing an Idealized MSA
    • How to Avoid
  • Risk: Underestimating the Required Investment
    • How to Mitigate
  • Pitfall: Changing Architecture While Learning New Processes
    • How to Avoid
  • Risk: Being Afraid to Fail
    • How to Mitigate
  • Pitfall: Failing to Put “Just-Enough Governance” in Place
    • How to Avoid
  • Pitfall: Expecting to Be “Done”
    • How to Avoid
  • Related Guidance

Gartner Recommended Reading

©2020 Gartner, Inc. and/or its affiliates. All rights reserved. Gartner is a registered trademark of Gartner, Inc. and its affiliates. This publication may not be reproduced or distributed in any form without Gartner’s prior written permission. It consists of the opinions of Gartner’s research organization, which should not be construed as statements of fact. While the information contained in this publication has been obtained from sources believed to be reliable, Gartner disclaims all warranties as to the accuracy, completeness or adequacy of such information. Although Gartner research may address legal and financial issues, Gartner does not provide legal or investment advice and its research should not be construed or used as such. Your access and use of this publication are governed by Gartner’s Usage Policy. Gartner prides itself on its reputation for independence and objectivity. Its research is produced independently by its research organization without input or influence from any third party. For further information, see Guiding Principles on Independence and Objectivity.

Already have a Gartner Account?

Become a client

Learn how to access this content as a Gartner client.