Enterprise Messaging with Apache Pulsar
Challenge
The client needed to consolidate a heterogeneous messaging landscape (Tibco Rendezvous, Kafka, ArtemisJMS) into a future-ready platform that is geo-redundant, highly available, and scalable, while staying open for future integrations.
Approach
I designed and implemented a multi-layer enterprise messaging platform based on Apache Pulsar, combining operational safety, automation, and governance:
- Cluster design with geo-redundancy and failover strategy
- Protocol support for Pulsar-native, Kafka interop, MQTT, and AMQP
- Governance model with tenants, namespaces, RBAC, and encryption
- Declarative object management via custom Ansible modules
- Evaluation of commercial offerings under digital-sovereignty criteria
- Custom tooling for health checks, data pumps, self-fencing, and load testing
- End-to-end observability in Prometheus/Grafana
Snapshot
- Industry: Industrial enterprise
- Time frame: 2024-2025
- Technologies
- Apache Pulsar
- Golang (custom tools and data pumps)
- Kubernetes / bare metal
- Prometheus / Grafana stack
- Ansible (custom Pulsar modules)
- TLS, JWT, RBAC
The platform delivers stable, high-throughput data streams and serves as a central integration layer for business-critical systems.
Do you have a similar project in mind?
With deep experience in messaging architecture and operations, I support organizations from design to sustainable implementation.
Get in touch