We're pleased to announce the general availability of Kong Insomnia 9.2. This release further expands on the features recently announced in Insomnia 9.0, with support for automatically generated fake values powered by the Faker.js library.

In many industries (finance and healthcare, to name a couple), regulations require the use of multi-factor authentication (MFA) to protect access to sensitive data and transactions. Also, an important executive order was issued, aimed at improving the cybersecurity posture within the US government by requiring all federal agencies to adopt MFA systems. Regulations and standards like these will continue to spread over more industries and transaction types.

In today's data-driven world, the ability to seamlessly connect, manage, and manipulate vast amounts of data is paramount for businesses and developers alike. Graph API stands at the forefront of this technological frontier, offering robust tools that facilitate complex data interactions within applications. This powerful API provides a framework for accessing and integrating data points in an intuitive and effective manner, supporting dynamic data structures across various platforms.

The service mesh architecture pattern has become a de facto standard for microservices-based projects. In fact, from the mesh standpoint, not just microservices but all components of an application should be under its control, including databases, event processing services, etc.

Things can get tricky when managing pre-paid, pay-as-you-go billing for monetized APIs. Three mechanisms must be in place for this type of billing to work: first, you need to be able to add credits to an account. Second, you need to be able to burn down those credits. Third, you need to be able to block users from accessing the API once they have run out of credits.

API-database coupling vs. traditional multi-layered architectures: what’s the difference and why does it matter? The main difference between direct API-database coupling and multi-layered architectures is that the former allows the API to interact directly with the database, minimizing latency and complexity, while the latter uses multiple layers to separate concerns.

Now that we have set up our API, integrated it with Kong, and connected Stripe with Moesif, we have the infrastructure to begin billing for API usage. Now, we will move into configuring Moesif with the pricing, metering, and access control/governance pieces of the API monetization journey. Let’s kick things off by setting up the prices we want to charge for API usage in Moesif.

As software systems become increasingly complex, observability — the ability to understand a system's internal state based on its external outputs — has become a critical practice for developers and operations teams. Traditional observability approaches struggle to keep up with the scale and complexity of modern applications. As the amount of telemetry data grows, it becomes expensive and complex to navigate. Enter AI and its promise to revolutionize observability.

Network Telemetry, in simple terms, is like having a conversation with machines or systems located far away. It’s about collecting data from these distant sources to better understand how they’re performing. Think of it as a health check-up, but for machines or systems instead of people. This technology plays a crucial role in a variety of fields.