Learn how the Fivetran REST API allows you to programmatically manage users, groups and connectors to scale data workflows and improve your overall security posture.

As engineers and architects, we automatically build resilience into platforms as far as possible. But what about the unknown failures? What about the unknown behavior of your platform? The philosopher, Socrates, once said “You don’t know what you don’t know”. What if I could tell you there is a way to turn these unknowns into knowns – a way to understand how your platform will behave to specific failure events…

We live in a digital economy where Application Programming Interfaces (APIs) are foundational elements for businesses to operate and grow. As rightly outlined by Gartner, APIs interconnect individual systems that contain data about people, businesses and things, enable transactions, and create new products/services and business models. The popularity of APIs has grown significantly in the last decade or so, but the history of APIs stretches back much further.

In our last blog post, we traced the evolution of APIs in the cloud age. The cloud age introduced the idea of an “API economy” — or the business practice of organizations exposing their digital services or information through the controlled use of APIs. While the API economy looks attractive today, we believe it will become even stronger in the future.

FIDO is a term that’s commonly heard of in the passwordless-authentication space. In this blog post, we’ll discuss how passwordless-authentication mechanisms first emerged, and also learn how FIDO authentication works.

Retail is a challenging industry. It is constantly evolving to reflect consumer preferences in product selection – but that is only part of it. As more people turn to online shopping, many retailers are using application programming interfaces (APIs) to remain competitive. Consumers have certain expectations of technology, so implementing digital transformation and APIs in retail has become less of an option and more of a requirement to attract and retain the modern customer.

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.

APIs can have a huge impact on your business, creating value and delivering new income streams. But they don’t always do so in the way you might have had envisioned at the outset. Which means, when it comes to API monetization, it can pay to be prepared for the unexpected.

Say you’re running a web service that requires input. In turn, the web service delivers it to another backend service. If the backend service isn’t available for an extended time, do you have a fail-proof system in place? This is where the circuit breaker design pattern comes in.