TL;DR: Connect your external REST interfaces (Kong) to your internal event mesh (built with Solace). Use Kong’s Solace plugins to turn requests into events, apply security and governance at the edge, and deliver low latency, observable data cost efficiently across clouds and data centres.
Why connect APIs and an Event Mesh?
Most enterprises operate two parallel worlds:
- Synchronous: REST APIs for partner and customer interactions at the edge.
- Asynchronous: Events for internal microservices, data streaming, and multi/hybrid cloud data movement.
Treating them as separate stacks leads to duplicated governance, inconsistent developer experience, and brittle point integrations. A unified approach makes events discoverable and governable like APIs, while REST endpoints gain freshness and scalability from event-driven delivery.
By integrating Solace Platform with Kong API Gateways, organizations can implement a cohesive “North-South” and “East-West” data fabric tearing down the silos of “async” and “sync” interactions.
A Transportation Network for Data and Events
Think of Kong Gateway as your Grand Central Station: it faces the outside world, provides standard RESTful access, checks tickets (auth), manages crowd flow (rate limiting), and posts clear signage (documentation).
Think of the event mesh you build with Solace as the highspeed underground rail network: it moves enormous volumes of data East–West across AWS, Azure, and on-premises data centres—with topic routing, backpressure handling, reliability, and location transparency.
Together, the station and rails give partners a simple, governed entrance to a complex, high-performance network—without partners having to learn the track layouts.
Gateway Convergence: Internal and External
Both event brokers and API gateways function as mediation layers. Your internal infrastructure – the event mesh– is optimized for efficient “East-West” movement between systems regardless of their location in AWS, Azure, GCP or on-premises. And Solace event brokers also act as internal multi-protocol gateways that perform protocol translation, for example allowing an IoT application to publish an event that an internal microservice consumes or an integration routes to a data lake or system of record.
For external partners, the Kong API Gateway serves as the entry point. It abstracts the complexity of the underlying rail network, providing a standard REST-based interface (for North-South traffic) to clients that do not have direct access to the internal mesh – such as partners, customers or other business units and subsidiaries.
Architecture Overview
Edge (North–South)
- Kong Gateway exposes REST endpoints to partners and customers.
- Policies (auth, quotas, schema/payload checks) are enforced consistently at ingress.
- Outbound callbacks use webhooks (or web protocols) so consumers get real-time updates.
Mediation Plugin (REST → Event)
- The Solace Upstream plugin maps REST requests to Solace messages (including headers/body, metadata).
- Persistent sessions funnel many requests efficiently into the broker—reducing connection churn and infrastructure cost.
Event Mesh (East–West)
- Solace Platform routes messages across topics to subscribers anywhere—AWS, Azure, and on-premises—without tightly coupling producers to consumers.
- Built in backpressure and QoS ensure slower consumers aren’t overwhelmed; replay/persistence patterns are available where required.
Consumers
- Internal applications subscribe to the relevant topics.
- Partners receive push notifications via webhooks or can consume using other web friendly protocols – such as WebSocket/SSE – if permitted.
What Architects Gain
Unified Governance at the Edge
You can apply one set of guardrails (auth, rate limits, validation, approval flows) before traffic hits the event mesh or internal synchronous services. Security, platform, and API teams operate from the same playbook regardless of sync/async API style.
Protocol Abstraction and familiar Developer Experience
Partners stay in the REST and Web API world; the platform performs REST to event mediation. Internally, you publish event APIs with consistent documentation and naming, and surface them in the same portal experience as REST APIs.
End-to-End Observability
You can instrument Kong and event brokers to trace events from external clients across API Gateways and the Event Mesh to internal applications and services allowing you to track latency, throughput and identify errors. These Findings help you right size policies and broker resources such as queues, and to catch hotspots early.
Performance & Cost Efficiency
You can enable your partners and other API consumers to move from heavy polling to event-driven updates. Persistent broker sessions and async delivery reduce connection overhead, smooth bursts, and avoid hammering slow backends.
AI-Readiness
As you are introducing agentic AI, use the event mesh as the reliable backbone for agent-to-agent communication and event triggered workflows, and use Kong AI Gateway to apply gateway level controls for AI traffic (routing, guardrails, sanitisation). This architecture provides the necessary real-time context ensuring AI agents have a reliable path to live enterprise data.
Implementation Impact: Global Retailer Case Study
This global retailer utilized the “Station and Tracks” model to build their Partner Portal, unifying REST and Event APIs for many partners. By utilizing the event mesh to bridge geographically distributed brokers (on-prem, Azure, Google Cloud) and Kong to manage the external interface, they significantly reduced integration overhead. Previously, the retailer had reduced onboarding of new transport service providers from 18 to 2 weeks by introducing the Solace Platform. The Solace and Kong integration provides full self -service to these partners reducing onboarding time significantly again.
Conclusion
Connecting Grand Central Station (Kong) to high-speed rails (Solace) gives you a unified real-time fabric: external consumers get secure, RESTful entry; internal services get decoupled, governed event streams across AWS, Azure, GCP and on-prem—with end-to-end observability and cost-effective scale. It’s a practical, proven way to make event APIs first class citizens in a RESTful world.
Resources
Explore other posts from category: API Management
Subscribe to Our Blog
Get the latest trends, solutions, and insights into the event-driven future every week.