Over a million developers have joined DZone.

How to Choose the Right Technology, Framework or Tool to Build Microservices

DZone 's Guide to

How to Choose the Right Technology, Framework or Tool to Build Microservices

Learn more about Microservices from Kai Wähner, and how to use several different technologies like Camel, Puppet, and Docker to best utilize them.

· Integration Zone ·
Free Resource

Last week, I gave a talk at a German conference (Karlsruher Entwicklertag 2015) about Microservices. The following slide deck shows plenty of different technologies (e.g. REST, WebSockets), frameworks (e.g. Apache CXF, Apache Camel, Puppet, Docker) or tools (e.g. TIBCO BusinessWorks, API Exchange) to realize Microservices.


Microservices are the next step after SOA: Services implement a limited set of functions. Services are developed, deployed and scaled independently. This way you get shorter time to results and increased flexibility.

Microservices have to be independent regarding build, deployment, data management and business domains. A solid Microservices design requires single responsibility, loose coupling and a decentralized architecture. A Microservice can to be closed or open to partners and public via APIs.

This session discusses technologies such as REST, WebSockets, OSGi, Puppet, Docker, Cloud Foundry, and many more, which can be used to build and deploy Microservices. The main part shows different open service frameworks and proprietary tools to build Microservices on top of these technologies. Live demos illustrate the differences. The audience will learn how to choose the right alternative for building Microservices. 

Key Messages

I used three key messages within my talk to explain the complexity and variety of different Microservice concepts:

–Integration is key for success of Microservices
–Real time event correlation is the game changer
–TCO and Time-to-Market are major aspects for tool selection

Slide Deck

soa ,devops ,soap ,web service ,integration ,esb ,docker ,microservices ,cloud

Opinions expressed by DZone contributors are their own.

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

{{ parent.tldr }}

{{ parent.urlSource.name }}