3,523 karma · joined February 16, 2009
-
To avoid increasing complexity in managing all these APIs we have added KONG [1] on top, so we can keep higher consistency and orchestrate common functionalities among multiple services. In some ways it's funny, because KONG "centralizes" a decentralized architecture but we needed one home base to always refer to or rely on,when most of the system started to live on the edges.
In space explorations you always have a mothership after all.
The whole thing is beautiful, from the low level of Go, up to the CSS.. it's not just a nice cover on top (like many other products)
We have embraced Nginx and built KONG[1] as the main API Gateway for managing our microservices. It made our transition much faster and easier since we were able to orchestrate common functionalities across services, such as logging and authentication, in a few lines of code.
[1] A month ago we've released Kong open source: https://github.com/Mashape/kong
I suggest to start from here to get up to speed: http://microservices.io/patterns/apigateway.html
Also, someone added Mockbin on Docker: https://registry.hub.docker.com/u/tomdesinto/mockbin/