Over a million developers have joined DZone.
{{announcement.body}}
{{announcement.title}}

3 Considerations for Transitioning From a Monolith to Microservices [Video]

DZone's Guide to

3 Considerations for Transitioning From a Monolith to Microservices [Video]

There are three considerations to keep in mind when transitioning to microservices: product maturity, tooling, and build incrementality.

· Integration Zone
Free Resource

The Integration Zone is brought to you in partnership with Cloud Elements. What's below the surface of an API integration? Download The Definitive Guide to API Integrations to start building an API strategy.

Microservices are gaining popularity as a way to break enterprise software apps into small, specialized units that work together to form the whole system.

But what apps are the best candidates, and how do you make the leap?

In this video, Rob Zuber, CTO of CircleCI, discusses three considerations to keep in mind when transitioning to microservices: product maturity, tooling, and build incrementality.

Interested in hearing more details? Watch Rob’s in-depth talk, “Managing the Transition from Monolith to Microservices.”

Your API is not enough. Learn why (and how) leading SaaS providers are turning their products into platforms with API integration in the ebook, Build Platforms, Not Products from Cloud Elements.

Topics:
integration ,microservices ,monoliths

Published at DZone with permission of Laura Franzese, DZone MVB. See the original article here.

Opinions expressed by DZone contributors are their own.

{{ parent.title || parent.header.title}}

{{ parent.tldr }}

{{ parent.urlSource.name }}