Integration Architect Kim Clark explains the inter-relationships among microservices and APIs, SOA, and agile, including when and where to use each or a combination.

In this video:

In these three videos, Integration Architect Kim Clark explains the inter-relationships among microservices and APIs, SOA, and agile, including when and where to use each or a combination.

Friends, enemies, or frenemies?

“Do microservices force us to look differently at the way we lay down and evolve our integration architecture or are they purely about how we build applications?”

In this webinar (above), Kim (along with help from Brian Petrini) answers this question and covers whether or not the technology is a new concept or an evolution of other ideas (or whether there is a functional difference between the two) and takes a close look at the relationship between it and other initiatives like APIs, SOA, and Agile. The pair provide a clear definition of the topic and in what circumstances the technology makes sense for an enterprise system.

Microservices or APIs: Which should I choose?

“By definition, an API is an interface. An interface decouples the caller from the implementation.”

In this video, Kim dives a little deeper into the comparison and describes the common misconceptions between the technology and APIs and provides clear, crisp definitions of both, concluding with a summary of the fundamentals.

Microservices or SOA: How to start an argument?

“Microservices relate to application architecture; SOA relates to the broader, enterprise-level service exposure.”

Finally, Kim explores the relationship between the topic and service-oriented architectures (SOA), outlining the strengths and weaknesses of both and how to decide where and when to use them in your project.

Resources for you

Microservices TV

Get the latest news, trends and tutorials on all things microservices.

Join The Discussion

Your email address will not be published. Required fields are marked *