The Microservice Myths You Shouldn't Believe

Mark Emeis

This edition of Software Confidential is by Mark Emeis, a founder of the CA Accelerator project, focusing on building tools to simplify complex microservice-based applications. Mark holds several software patents and is a member of the Security Patent Review Board.

Microservice Architecture is a Fad.

The container, the essential component of microservice architecture, is not a new phenomenon—and it is built to last. The type of process isolation they provide can be traced back to the 1970s, but the container paradigm is by far the best implementation to date. They support most languages, run across all key operating systems, and are immutable—good indicators that they will be around for some time.

Microservices are Only Good for New Apps.

Microservices represent a new take on the approach to software development introduced by service oriented architecture (SOA). Microservices and SOA both upset the monolithic paradigm of enterprise architecture by using loose coupling to integrate components. Therefore, a great way to get started with microservices is to decompose a monolithic app into multiple loosely coupled containers.

Microservices Only Work for SaaS.

Microservices provide a great way to build SaaS apps. But it’s not true that the benefits of microservices are limited to SaaS. Some of the most successful digital enterprises have realized advantages and benefits by building all on-premise apps using container-based microservice architectures. The advantages and benefits routinely outweigh the costs incurred by embracing microservices.

By Mark Emeis | 21 Feb 2018

Want to create an agile business?

We’ve got even more insights, guidance and tips.

Read more >