Microservices development presents integration, deployment challenges

Solving microservices modern integration issues

In the development world, new advancements such as microservices, containers and APIs are somewhat of a double-edged sword. How will they fit in with existing architectures, often based on traditional concepts like SOA? How should they fit into a continuous integration strategy? And as APIs become essential to data integration, what management challenges will follow? These are just a few of the challenges that lurk in the world of modern integration.

Many businesses, for example, may be trying to determine how they can merge SOA with microservices. But since microservices evolved from the REST model, they represent a completely different architecture paradigm than SOA. Consultant Tom Nolle points out that these differences could cause significant issues, including processing delays. His solution rests in the establishment software methods and design patterns that accomplish clearly defined operational goals.

Another issue is the process of enabling continuous integration via containers. One solution is the creation of logically interdependent container communities. It's then important to reference those communities when mapping container deployments, because integration component communities must stay as close in line with production deployment as possible.

And we can't forget about APIs. Journalist George Lawton says 2016 was the year of the B2B API. But enabling access to B2B API services is not a free ride. The greatest challenge will be cutting through market hype to determine which APIs and API management services can deliver real value.

This handbook will not only highlight the biggest challenges of modern integration, but also help you understand what steps need to be taken to successfully combine microservices with SOA.