Microservices and an API Gateway

With all the talk of Microservices, this very discussion came up in my office.
As we make services more granularized, the Client Browser becomes the focus of being the actual application: aka Single Page Application written in JavaScript: WebComponents, Angular.js, Ember.js adn the like.
This blog link is a fast read discussing at a high level the need for an API layer to hide specific implementation details from external clients, and provide an extra layer of protection from external calls.

Why Do Microservices Need an API Gateway? – @DZone

Advertisements

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s