Moreover, integrating rate limiting can thwart DDoS attacks, and schema validation can prevent malformed requests, ensuring only legitimate and well-formed traffic reaches your serverless functions. Tools like Amazon API Gateway, Azure API Management, and Google Cloud Endpoints offer these capabilities, allowing you to set up custom authorization workflows and request validation rules that align with your security... - Source: dev.to / about 1 month ago

AFAIK, API Gateway is just managed Cloud Endpoints, which are just ESPv2 containers. Cloud Endpoints are still a thing but I would agree that they are a bit dead, as they don't support OpenAPI v3, which was released in 2016. See this support ticket from 2018: https://issuetracker.google.com/issues/78271318?pli=1. Source: over 1 year ago

For reference: https://cloud.google.com/endpoints. Source: almost 3 years ago

Use Cloud Endpoints in front of your service, which gives more options for authentication, including JWT. Here's an intro (the English is poor, but advice is sound.). Source: about 3 years ago

This happened when I was working for one of my previous employers. I had just joined the company and was working on a microservice that was consuming a REST api exposed by another microservice. There was this JIRA ticket I was working on and I was not sure about the data model exposed by this REST api call. At this point in time the adoption to OpenAPI / Swagger / RAML was just beginning. I was new and was... - Source: dev.to / over 2 years ago

Provide consistent and easy-to-use documentation. Provide an OpenAPI or RAML file that describes your API and the endpoints. Also, provide easy-to-use interactive online API documentation like Swagger if possible. - Source: dev.to / almost 3 years ago