There are key players in the market that offer endpoint services including Amazon Web Services, Google ,IBM and more . Google has APIGEE as the strongest contender for dynamic endpoint services. Google cloud endpoints is the traditional , stable and feature equipped endpoints service . It helps you create, deploy, protect, monitor, analyze, and serve your APIs using the same infrastructure Google uses for its own APIs.
This blog will help you understand why you should use cloud endpoints services instead of deploying your prepared APIs on a server the traditional way.
Here we have explained a brief comparison of Google cloud endpoints framework with Google App Engine against traditional way of creating apis.
The same applies to Google cloud endpoints framework with kubernetes/ VM .
- API calls :- We have two applications , one web client and one mobile app which send requests to endpoint urls.
- Endpoint framework provides us with a mechanism to prepare apis and deploy them . It is just like python flask / java jersey . Here we have a yaml file (just like an xml file) that provides the initial configuration .Google App Engine reads this to understand head routing, python/java versioning , latest libraries used for connecting with database .
While the framework provides annotations that can be used in python code to understand the type of request, path of request and method to be called.
Endpoint allows us to setup a server of these apis. At 2. , Endpoint management which comes along with Endpoint framework which sends token to Service control
3. . If you configured your API to require an API key or authentication, Service Control checks to see if the request is permitted and sends a response back to the Endpoints Management module.
4. If the request is permitted , it is sent back to Endpoints framework.
5. Endpoints framework accordingly redirects it to our api code . It reads the route , loads the compiled python file against the route. It then executes the relevant code.