How BT Group Built a Smart Event Mesh with Confluent
Blog post from Confluent
BT Group’s Digital Integration team developed a Confluent-based event streaming platform to support real-time, large-scale data movement across its on-premises, AWS, and Google Cloud environments. Beginning in 2020, the initiative established Common Event Brokers using Apache Kafka to decouple applications and enable use cases such as network monitoring, machine-learning analytics, CRM change-data capture, and event-driven service reconciliation. Rather than adopting a centralized hub-and-spoke model or a fully independent mesh, BT chose a Smart Event Mesh architecture in which clusters communicate directly when needed while a central control plane automates synchronization, governance, and onboarding through Confluent Cluster Linking, Kafka Connect, and Schema Registry. The next phase aims to provide organization-wide event discovery, federated self-service, automated topic and access management, stronger governance, and proactive monitoring, while BT evaluates moving its self-managed GCP deployment to Confluent Cloud and expands the platform to support customer-facing Kafka services.
| Trend | Post Mentions | Total Month Mentions | Posts | Companies | MoM |
|---|---|---|---|---|---|
| Real-time | 28 | 2,985 | 789 | 223 | +25% |
| Data Pipeline | 1 | 690 | 197 | 79 | +34% |
| Vector Search | 1 | 2,337 | 296 | 106 | +34% |
Use this post, company, and trend context to find content marketing opportunities, perform competitive analysis, or address product feature gaps via the Plushcap MCP server or the Plushcap API.