Define a Docker image relying of Mashape Kong to act as API Gateway for the BenchFlow Services #6
Description
We are going to rely on Mashape Kong for handling the interaction between the client and all the BenchFlow services.
Some of the reasons why Mashape Kong is a good solution for us:
- It is based on NGINX, a battle tested HTTP and reverse proxy
- It is made for scale
- It handles authentication
- It well documented
- Docker is an official and maintained deployment method
- It relies on Cassandra, as we do
- It has a plugin architecture, it means we can eventually build our own plugins (e.g., an hello world example)
The authentication will be needed only between the client and the API Gateway, since we are going to rely on the Tutum's Overlay Networking for the communications among the other services. This means we don't need to expose the BenchFlow services to the internet, and the communication among them will be secured out of the box by the Tutum's network (if we need to access hem, we can use the endpoints provided by Tutum).
Some good references to read before the implementation: