A multi-component broker with no vendor behind it
Pulsar is three systems in a trench coat -- brokers, BookKeeper and ZooKeeper. Running it in production without a support relationship means owning all three when something goes wrong.
Challenge
Pulsar's architecture separates serving from storage, which is a strength operationally and a liability at 3am: a problem can live in the broker, in BookKeeper, or in the coordination layer, and the three fail in ways that look alike from the outside.
Environment
Apache Pulsar in production, with BookKeeper and ZooKeeper underneath, no commercial support contract.
Approach
OSSeva covers the whole stack -- broker, BookKeeper and the coordination layer -- with CVE patching and a contractual response SLA rather than support scoped to one component.
What this delivers
One support relationship covering all three layers, instead of three unowned components.