Systems | Development | Analytics | API | Testing

At NodeSource, we live and breathe Node.js and are passionate about performance and security. We understand that for developers and platform teams, managing the security and compliance of dependencies is a mission-critical task. However, the tools designed to help can sometimes become part of the problem. Today, we’re proud to introduce NodeSource Certified Modules v3 (NCM v3): a complete rearchitecture of our module scanning and observability engine.

If you have spent any time working with Elixir in a production setting — or even just building a side project — you've likely encountered a stack trace. Stack traces can appear intimidating at the outset, especially since Elixir's error messages are often more detailed than those in other languages. However, they are a powerful tool for understanding what went wrong in your code. Early in my Elixir journey, I found stack traces to be a bit overwhelming.

Software development isn’t what it used to be, and that’s a good thing. What was once a linear code-and-release process has evolved into a dynamic, AI‑powered, security-first ecosystem spanning cloud, edge, and compliance workflows. In 2024, the global software development market reached $403.6 billion and is expected to climb further, driven by AI, cloud-native architectures, and embedded automation.

APIs are the backbone of modern systems, but when they fail, the impact can be catastrophic. Fault injection testing helps you prepare for these failures by simulating disruptions in a controlled way. This practice ensures APIs remain reliable and can recover gracefully under stress. Here's what you need to know.

Picture this: It's 3 AM, and your phone erupts with alerts. Within minutes, you're drowning in a tsunami of notifications—hundreds of them—while your company's critical services hang by a thread. Your monitoring dashboard looks like a Christmas tree gone wrong, every light blinking red, and you have no idea where to start. Sound familiar?

Telemedicine app development is a trend that has taken the digital healthcare world by storm! And, we’re not joking about this because it’s the reality of today, tomorrow, and beyond the healthcare industry! So, what do you imagine when you think of telemedicine in general? A consultation app? Possibly some kind of a tidbit related to new offers or something like that? However, we can assure you that there is so much more to telemedicine than meets the eye.

Analyzing logs in data pipelines is essential for maintaining system performance, troubleshooting errors, and ensuring compliance. Here's what you need to know: Why It Matters: Logs help identify bottlenecks, resolve errors, and optimize performance. They are also critical for audits and compliance. Challenges: High log volume, varying formats, and security risks make analysis complex. Solutions: Standardize log formats with timestamps, log levels, and metadata.

Securing APIs requires managing who can access resources and under what conditions. Two primary models stand out: Role-Based Access Control (RBAC) and Attribute-Based Access Control (ABAC). Here's the key takeaway: RBAC assigns permissions based on predefined roles, making it simple to manage in structured environments. ABAC evaluates multiple real-time attributes for dynamic, granular control, ideal for complex or evolving scenarios.

In the last two parts of this series, we discussed How to Strengthen a ReAct AI Agent with Kong AI Gateway and How to Build a Single-LLM AI Agent with Kong AI Gateway and LangGraph. In this third and final part, we're going to evolve the AI Agent with multiple LLMs and Semantic Routing policies across them. In this blog post, we'll also explore new capabilities introduced in Kong AI Gateway 3.11 that support other GenAI infrastructures.