INFO Technology RadarINFO Technology Radar

Microservices

This item was not updated in last three versions of the Radar. Should it have appeared in one of the more recent editions, there is a good chance it remains pertinent. However, if the item dates back further, its relevance may have diminished and our current evaluation could vary. Regrettably, our capacity to consistently revisit items from past Radar editions is limited.
Adopt

This is now such a given (also in the industry) that we no longer feature it on our tech radar.

A microservices architecture is preferred over traditional monolithic architectures because it typically increases agility and time-to-market. Our preferred cloud vendors offer excellent support for microservices container architectures using vendor-specific services and/or Kubernetes solutions. For more background see: Why you should use Microservices Architecture for your applications and The importance of loose coupling in microservice architecture.

Adopt

A microservices architecture is preferred over traditional monolithic architectures because it typically increases agility and time-to-market. Our preferred cloud vendors offer excellent support for microservices container architectures using vendor-specific services and/or Kubernetes solutions. For more background see: Why you should use Microservices Architecture for your applications and The importance of loose coupling in microservice architecture.

We also encourage you to consider serverless, potentially as part of an event-driven architecture.

Adopt

A microservices architecture is preferred over traditional monolithic architectures because it typically increases agility and time-to-market. Our preferred cloud vendors offer excellent support for microservices container architectures using vendor-specific services and/or Kubernetes solutions. For more background see: Why you should use Microservices Architecture for your applications and The importance of loose coupling in microservice architecture.