Systems | Development | Analytics | API | Testing

JSON Web Tokens (JWTs) secure communication between parties over the internet by authenticating users and transmitting information securely, without requiring a centralized storage system. In this article, we'll explain what JWTs are and give a high-level overview of how they work. We'll also implement a JWT-based authentication system by creating a to-do list API using Flask.

As your user base expands, so does the volume and variety of push notifications you need to send. Whether it’s transactional alerts, updates, or personalized messages, publishing notifications for thousands - or even millions - of users can quickly become a bottleneck. The more you grow, the more important it becomes to have a scalable, efficient push strategy.

Regular expressions are usually not top of mind when you think of performance bottlenecks in your application, but inefficient patterns or sub-optimal use of the APIs can make them slow. A wonderful learning opportunity for this is a recent roughly factor of 2x performance improvement patch to Doctrine DBAL’s SQL Parser. This patch was submitted by Soner from Shopware fame, thank you to him.

Process automation has been around for decades, but the tools under this technology umbrella have multiplied over the years. Robotic process automation (RPA) was an early tool for handling simple, routine tasks, and it’s still powerful to have in your intelligent automation arsenal. But when technologies like intelligent document processing, business rules, and workflow orchestration entered the scene, they brought new capabilities to the process automation suite.

Usage-based pricing has long been the default for APIs—straightforward to implement and easy for customers to understand. You charge based on consumption: API calls, compute time, or data volume. It is predictable, measurable, and scales well with usage. But as APIs become more intelligent—especially in AI-driven platforms—raw consumption no longer remains a reliable proxy for customer value. A user can rack up thousands of API calls and still achieve nothing meaningful.

NGINX with OpenResty offers unmatched performance for serving APIs (application programming interfaces) at scale, with the added benefits of the open-source ecosystem. It’s fast, flexible, and production-proven—an ideal choice for scalable web platforms and high-throughput APIs. But even the most reliable platform can leave teams blind to what matters: real-time API usage, user behavior, and production errors.

The crash-proof app doesn’t exist. It never has, and it probably never will. Because apps can crash for all kinds of reasons, some of them impossible to foresee. No matter how well we build them, crashes are going to happen to our apps. So, as devs, we need to know how to react to a crash when it happens. And in this context, understanding crash reports is crucial. They provide the clues we need to put the pieces together.

API request logging is essential for secure and efficient APIs. It helps track performance, detect security threats, and meet compliance standards. Here's a quick breakdown of what you need to know: Why It Matters: Logging provides real-time insights, audit trails for investigations, and supports compliance.

Model Context Protocol (MCP) is an open protocol that standardizes how applications provide context to large language models (LLMs). It’s becoming a foundational layer in many AI-native workflows, especially when working with real-time or continuously updating data sources. We're excited to announce that Choreo now supports the deployment of MCP servers, empowering developers to integrate AI capabilities more efficiently into their applications.