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:
How APIs Are Bringing Agility To The Cloud

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:
Internet of Things made simpler with SAP API Management

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.

 



Data Innovation Summit 2017

30
Mar
2017
Data Innovation Summit 2017

30% off with code 7wData

Read Also:
"Companies are finally able to start a data culture"

Big Data Innovation Summit London

30
Mar
2017
Big Data Innovation Summit London

$200 off with code DATA200

Read Also:
Microservices for Internet of Things Edge Devices

Enterprise Data World 2017

2
Apr
2017
Enterprise Data World 2017

$200 off with code 7WDATA

Read Also:
How to build a smart city using mobile technology and IoT

Data Visualisation Summit San Francisco

19
Apr
2017
Data Visualisation Summit San Francisco

$200 off with code DATA200

Read Also:
How Semantic Data Analytics Benefits Population Health Management

Chief Analytics Officer Europe

25
Apr
2017
Chief Analytics Officer Europe

15% off with code 7WDCAO17

Read Also:
Using OpenStack To Build A Hybrid Cloud With AWS
Read Also:
The Data Integration Journey to the Cloud

Leave a Reply

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