Author: admin

As developers/architects, we often use caching mechanisms at our API Layer to reduce the strain we put on our backend services. Some of the backend service operations, however, cannot be cached by nature and we need to pass-through user requests to them. When these operations are considered as “expensive,” we should apply some protection mechanisms to avoid possible service degradations.

The “expensive” service operations which may not be cached include are:  https://goo.gl/1JK9fx #DataIntegration #ML

ICYDK: Part I – OAuth2 in a Nutshell

OAuth2 is a framework, defined here. It’s not a protocol, because the RFC doesn’t contain enough implementation specifics. I say this with the understanding that the line between protocol and framework is a blurry one…

The RFC first defines four roles: https://goo.gl/wXmdAF #DataIntegration #ML

Logging has always been in the background of other stops along the API lifecycle, most notably the API management layer. However, increasingly, I am recommending pulling logging out of API management and making it a first-class citizen, ensuring that the logging of all systems across the API lifecycle is aggregated, and accessible, allowing logs to be accessed alongside other resources. Almost every stop in this ‘Basics of an API Lifecycle’ series will have its own logging layer, providing an opportunity to better understand each stop, but also side by side as part of the bigger picture.

There are some clear leaders when it comes to logging, searching, and analyzing large volumes of data generated across API operations. This is one area you should not be reinventing the wheel in, and you need to be leveraging the experience of the open source tooling providers, as well as the cloud providers who have emerged across the landscape. Here is a snapshot of a few providers who will help you make logging a first class citizen in your API lifecycle. https://goo.gl/XWC5K6 #DataIntegration #ML