Systems | Development | Analytics | API | Testing

We are proud to announce the release of Apache Kafka 4.0. This release contains many new features and improvements. This blog post will highlight some of the more prominent ones. For a full list of changes, be sure to check the release notes.

This is Chapter 2 of our journey of non-functional testing with Otto Perf. You can read Chapter 1 if you have missed it. Authors note The article is in the OctoPerf Blog pages Otto had previously got to the point where he had defined a set of non-functional requirements and risk assessed these with the programme team.

With the release of Node.js v23.6.0, developers can now use TypeScript natively without additional transpilation tools like ts-node or manual compilation steps. This milestone significantly streamlines development workflows, simplifying build processes and improving the overall developer experience by reducing complexity.

We’re excited to announce the general availability of Kong Insomnia 11! This release introduces third-party vault integrations for enhanced security, an all-new Git sync experience for more seamless collaboration, and support for multi-tabs to improve efficiency within the Insomnia application. Keep reading to learn more.

When your company deployed its first large language model last quarter, your CTO probably didn't mention you'd need entirely new tools to understand what's happening under the hood. But here we are. AI Observability isn't just another tech buzzword—it's the difference between confidently leveraging AI and crossing your fingers hoping nothing breaks.

When it comes to ensuring software quality, having a well-defined Test Plan and Test Strategy is crucial. As a software developer or QA professional, understanding the differences between these two concepts and how to write a Test Plan or execute a test strategy effectively can significantly improve your testing process.

One method that developers use to submit code modifications for evaluation is known as pull requests (PRs). We discussed the advantages of testing PRs in software development in a previous post but before merging into the main branch, they give team members a chance to talk about the changes, make suggestions, and accept or reject the code. To keep code quality high and make sure that the team reviews all changes, this approach is essential.