Systems | Development | Analytics | API | Testing

Observability has become critical to ensuring the effective monitoring of application and system performance and health. It focuses on understanding a system’s internal state by analyzing the data it produces in the context of real-time events and actions across the infrastructure. Unlike traditional monitoring, which mainly notifies you when issues arise, observability offers the tools and insights needed to determine not only that a problem exists but also its root cause.

In this episode, Derric Gilling chats with James Higginbotham, founder of LaunchAny, about designing successful API strategies that drive business value. James dives into his “Align-Define-Design-Refine” (ADDR) methodology, a framework that guides organizations from initial business alignment through iterative API design and deployment.

The API landscape is constantly evolving, and developers like us crave tools that streamline data fetching and boost performance. For years, REST reigned supreme, but a challenger has emerged – GraphQL. So, is GraphQL truly a "better version" of REST? Let’s explore this question through code and performance comparisons.

API’s have become the backbone of modern digital ecosystems, enabling seamless integration and interaction between diverse systems, applications, and services. Organizations increasingly rely on APIs to deliver robust functionality, enhance user experiences, and drive operational efficiency. Additionally, APIs are playing an even greater role in the future of AI-driven systems.

Kong is ranked number 1 on the G2 Momentum Grids for API Management and API Development for Spring 2025. And users seem to agree with the glowing assessment: Kong is currently the highest-rated tool based on user satisfaction in the categories of API Management and API Development on G2. We think there are plenty of reasons why Kong is king when it comes to API management and API development. But don't just take our word for it.

Recent leaks have once again brought API and data security concerns into the spotlight. Specifically, the leaks pointed at the following as major areas to consider when thinking through your API and data security strategies: When considering the above, it’s critical to think about best practices across every stage of the API lifecycle, starting with the initial phases of API design and testing.

Software development has always evolved with new paradigms to meet the growing demands of modern systems. One of the most significant shifts has been the adoption of microservices. Emerging in the early 2010s, this architectural pattern moved away from monolithic applications in favor of smaller, independent services that interact with each other over a network.

APIs (application programming interfaces) have transformed how we build modern software systems. As our digital experiences become more modular and interconnected, APIs power mobile apps, partner integrations, and internal services. Most companies now expose APIs not just for technical access, but as part of a larger API business model. But simply deploying APIs through a gateway like Gravitee doesn’t suffice.