Day: October 31, 2018

#ICYDK: API Gateway provides a feature to limit the number of requests a client can make per second (rate) and per day/week/month (quota). Rate limiting is very useful to protect your system from resource starvation caused by a client flooding your system with requests. Quotas are more useful to protect against data scrapers or to limit the number of expensive operations a client can perform without paying appropriately.

You have to combine two features of API Gateway to implement rate limiting: Usage plans and API keys. API keys are used to identify the client while a usage plan defines the rate limit for a set of API keys and tracks their usage. Clients are expected to send the API key as the HTTP X-API-Keyheader. However, what about using a path parameter to identify the client like /v1/some-client-id/task or a query parameter like /v1/task?clientId=some-client-id? In this article, you learn to use a Custom Authorizer to extract a parameter from the path and use the value as the API Key. You can follow the same approach to extract the API Key value from a query parameter or the body. https://goo.gl/a9uoD7

#ICYDK: We interviewed Enno Runne, team lead on the Alpakka project at Lightbend, about his career, the evolution toward instantaneous data via Alpakka, and his upcoming talk at Reactive Summit next week.

First of all, let’s talk about what your background is, and what initially drew you to systems integration. https://goo.gl/qscsQT