InfoQ Homepage Realtime API Content on InfoQ
Articles
RSS Feed-
Real Time APIs in the Context of Apache Kafka
Events offer a Goldilocks-style approach in which real-time APIs can be used as the foundation for applications which is flexible yet performant; loosely-coupled yet efficient. Apache Kafka offers a scalable event streaming platform with which you can build applications around the powerful concept of events.
-
Four Case Studies for Implementing Real-Time APIs
API calls now make up 83% of all web traffic. Competitive advantage is no longer won by simply having APIs; the key to gaining ground is based on the performance and the reliability of those APIs. This article presents a series of four case studies of how real time APIs were implemented.
-
Load Testing APIs and Websites with Gatling: It’s Never Too Late to Get Started
Conducting load tests against APIs and websites can both validate performance after a long stretch of development and get useful feedback from an app in order to increase its scaling capabilities and performance. Engineers should avoid creating “the cathedral” of load testing and end up with little time to improve performance overall. Write the simplest possible test and iterate from there.
-
Realtime APIs: Mike Amundsen on Designing for Speed and Observability
In a recent apidays webinar, Mike Amundsen, trainer and author of the recent O’Reilly book “API Traffic Management 101”, presented “High Performing APIs: Architecting for Speed at Scale”. Drawing on recent research by IDC, he argued that organisations will have to drive systemic changes in order to meet the upcoming increased demand of consumption of business services via APIs.
-
The Challenges of Building a Reliable Real-Time Event-Driven Ecosystem
Globally, there is an increasing appetite for data delivered in real time; we are witnessing the emergence of the real time API. When it comes to event-driven APIs engineers can choose between multiple different protocols. In addition to choosing a protocol, engineers also have to think about subscription models, too: server-initiated (push-based) or client-initiated (pull-based).