Systems | Development | Analytics | API | Testing

Picture this: It's 3 AM. You’re on-duty in case there is an outage. A team in the other part of the world merged PR and released a new version of K2K Replicator and it crashed. Consumer group lag is spiking to the universe. You’re paged & woken up, went to your laptop, the team already reverted PR, things are stabilising, but what really happened, you have to investigate now as postmortem has to be done.

Non-crashing bugs don’t make your app crash, but they can ruin the user experience and hurt your app’s ratings. Fixing these issues is critical to keeping users happy. Here’s a quick rundown of the most common non-crashing bugs and how to address them.

Concurrency means running multiple tasks at the same time, and it’s a great way to ensure our apps stay responsive. Swift 5.5 introduced structured concurrency and the closely related concept of async/await to improve the management of asynchronous code, part of a wave of changes designed to ensure simpler code, improved error handling and automatic task lifecycle management.

Over the past few years, model providers have invested heavily in “guardrails”: safety layers around large language models that detect risky content, block some harmful queries, and make systems harder to jailbreak.

This blog expands on insights Amjadh Ifthikar shared during his WSO2Con Asia 2025 presentation. Watch the full session here.

Have you ever observed an application that was completely functional, and suddenly it starts lagging at peak usage? Most teams are concerned with functionality first and performance under load second. Open source load testing tools expose your application’s bottlenecks before your users notice them. In this blog, we explain how these tools work, compare their features, and discuss best practices.

The EU AI Act is here, and for many enterprises, it represents a massive coordination challenge. As the world’s first comprehensive AI law, it mandates strict governance on transparency, risk management, and data quality. For platform engineers and architects, the immediate question is operational: How do we comply with these new regulations without forcing every developer to rewrite their applications?