Systems | Development | Analytics | API | Testing

This is part one of a series exploring how Kong AI Gateway can be used in an AI Agent development with LangGraph. The series comprises three parts.

The Model Context Protocol (MCP) is quickly becoming a foundational layer for AI systems. It enables large language models and AI agents to interact with external tools and data sources over standardized JSON-RPC interfaces. By doing so, MCP transforms how intelligent applications consume APIs. Reading local files, controlling IoT devices, orchestrating backend workflows—MCP servers act as structured gateways between AI and your business logic.

Picture the scene. You're sitting in yet another budget meeting, and someone inevitably pipes up with the golden question: "Why are we paying for seven different tools when we could just use one?" Everyone applauds. Confetti bursts from the ceiling. There’s a cake for some reason. That’s the siren song of vendor consolidation. It's everywhere these days, and honestly? It makes sense. Finance loves it because it’s cost savings that can be easily represented as a budget line item.

Imagine a world where every backend, legacy system, cloud database, and app is instantly connected—no manual coding, no ongoing maintenance headaches. As businesses rush to unlock value from data, API gateways are becoming critical infrastructure. The most advanced platforms now go beyond traditional API management—bringing AI, automation, and security into the integration layer.

The Perforce 2025 State of Automotive Software Development Report revealed that automotive companies are most concerned with quality, safety, and security.

At NodeSource, we’ve always been committed to making the Node.js experience secure, stable, and production-ready for teams around the world. Today, we're announcing a key change to how we serve and support our Node.js binary distributions, and it comes with something new: Extended Support.

A detailed Software Requirements Specification (SRS) document is key to building software that meets both business needs and user expectations. Clear, concise, and executable requirements align project teams, offer clarity on functionality, and act as a single source of truth throughout development. Whether you're using agile, waterfall, or a hybrid approach, this guide will help you craft clear, complete, and testable requirements.

Before we get started on WebSocket integration, it’s worth quickly explaining how building real-time mobile apps used to work – and why issues with lag and latency led engineers to turn to WebSockets instead. Engineers building real-time Android apps struggled to make sure updates were reflected immediately when a user sent them. To solve this, they tried polling, which meant firing off a GET request to the server, say every five seconds, to a /messages endpoint.