Using Microservices Architecture as API Enablement Strategy

Using Microservices Architecture as API Enablement Strategy

Using Microservices Architecture as API Enablement Strategy

Today Microservices architecture has become hype topic in software development industry.It is an approach to modularity which functionally decomposes an application into a set of services.  The development teams can adopt the most appropriate technology stack in order to resolve specific issues. The microservices architecture also improves services scalability by enabling features such auto-scaling and micro-container approach.

API’s and Microservices are so related once the most common facade are API interface uses fully compliant RESTful services. But nowaday we are still facing issues when needs to integrate with legacy systems to externalize its functionalities as services once the most systems does not expose standards protocols such as Web Services or REST Interfaces. Let’s explore this issue.

The most companies desire to expose API’s internally or externally but their systems or application were not built for this purpose. The most applications are based on the following architecture:

When facing this kind of scenario, it is a common approach build an adapter component to expose the service with standard protocol. This component should look like the diagram below:

Read Also:
Datera emerges from stealth to offer another take on cloud scale-out storage

The service adapter is the key component of solution since it will enable legacy service externalization. To provide this expected standardization, the following capabilities should be implemented:

As service adapters are considered kind of integration applications, they should follow an architectural style in order to be compliant with common standards. The architectural style that best suite the above capabilities and others commons requirements is the Microservice approach.

Once decided that service adapter implementation are based on Microservice Architecture style some capabilities are required such as:

Some frameworks has the most of capabilities listed above. The recommend are:

Another crucial capability when enabling API endpoints through Microservice implementation is fully integration capability with legacy systems. This kind of feature requires specific frameworks which implements enterprise integration patterns. The recommendation here is use the most famous Java framework called Apache Camel.

Once the package were built, it need to be deployed. The recommended strategy is deploy it into a PaaS (Platform as a Service) because it offers some built-in features such as:

Read Also:
A CIO writes (sort of): I’m terrified of cloud lock-in

Also, another two crucial capabilities should be provided:

The main market PaaS offering should be considered to be used as deployment strategy are:

Other choices to be considered areAmazon Elastic BeanstalkandGoogle App Engine.

 



Predictive Analytics Innovation summit San Diego
22 Feb

$200 off with code DATA200

Read Also:
Why Microservices Should Be Event-Driven
Read Also:
Scala, the Language for Data Science
Big Data Paris 2017
6 Mar
Big Data Paris 2017

15% off with code BDP17-7WDATA

Read Also:
What Catalog Shopping Can Teach Us About Data
Big Data Innovation Summit London
30 Mar
Big Data Innovation Summit London

$200 off with code DATA200

Read Also:
6 causes of application deployment failure

Leave a Reply

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