First published on The New Stack. The pandemic has accelerated the shift towards digital channels for banking, retail, and a host of other services. As a result, businesses are shifting their digital transformation initiatives into overdrive in order to meet customer demand for online interactions, which should be both inviting and secure. APIs act as key drivers behind most successful digital enterprises.
An API gateway lets API calls enter and leave to reach their corresponding destination points, better known as microservices, in a system. An API gateway is mainly responsible for routing API calls. Its secondary responsibilities include security, caching, load balancing, rate-limiting, dynamic discovery and routing, management, and scaling the number API calls.
Finastra has ambitious goals – to open up the world of finance. As Joey White, SVP of technology for Finastra, says, “The future of finance is open. All of the currently closed systems within banking will need to open to serve a digital future.” To him, open means understanding what you don’t know, specifically, the particular modality of use and that change is the only constant.
API providers need to understand how their consumers are using their APIs. Usage metrics are essential because they tell you about API adoption, how your API is growing over time, and which endpoints are seeing more (or less) use. When you look at API usage metrics, you should be measuring the active users on your API in the sense that most closely aligns with your service.
In this article, we are going to explore why the Stripe developer experience is so passionately supported by thousands of developers globally. One of Stripe’s missions is to increase the GDP of the internet, and over the last decade, they’ve successfully executed 250 million API requests per day and over 91 billion requests per year through their APIs.
