Systems | Development | Analytics | API | Testing

The API Waterfall is a sequentially and methodically defined approach for managing data flows and integration of services in software development. Aligned to the traditional waterfall methodology, the architectural model essentially targets a step-wise flow of events where each stage depends on the completion of the previous step.

In k8s world every resource created via controller. Like there are inbuilt controllers for pods, deployments , replica set etc. So basically, Controllers are nothing but a control loop that continuously monitor the state of the cluster and take actions to bring the cluster into the desired state. The resources have a spec that provides the desired state. The controller checks the current states.

Observability refers to understanding a system’s internal state by examining its external outputs, like logs, metrics, and traces. Borrowed from control theory, it’s the ability to infer what’s happening inside a system without direct access. To visualize observability, consider the human body. We don’t need to open it up to understand its internal state. By measuring external signals like body temperature, heart rate, or blood pressure, we can infer what’s happening inside.

Kong Konnect is Kong’s infrastructural SaaS solution. We run the control planes and API management applications for the data planes (API gateway and mesh) that are run by our customers to power their APIs. Some of the most critical traffic in the world goes through these data planes. The criticality of Konnect and therefore our customer’s uptime expectations of Konnect are very high.

In the process of developing software, designing and performing testing is a critical aspect of ensuring high software reliability, improving software quality, and deploying strong fit and function. The shift-right testing approach moves testing to later in your production cycle as a way of doing this with more accurate user data and post-production testing practices. Also known as “testing in production,” with shift-right, you test software after it has been deployed.

In the process of developing software, designing and performing testing is a critical aspect of ensuring high software reliability, improving software quality, and deploying strong fit and function. The shift-right testing approach moves testing to later in your production cycle as a way of doing this with more accurate user data and post-production testing practices. Also known as “testing in production,” with shift-right, you test software after it has been deployed.

Today — alongside the announcement of Kong Insomnia 10.2 — we're excited to introduce two new Kong Insomnia enterprise capabilities that will improve user management at scale across every organization. These new features are available to use for every existing enterprise customer, and they complement existing advanced user management capabilities like EE SSO and SCIM. Let’s take a look at each of the new capabilities.

Kong Insomnia 10.2 is now generally available with some exciting new features and improvements! As usual, we strongly recommend upgrading to this latest version and to always use the most recent release of Insomnia.