Loading content
Apache Pulsar is a flexible, scalable, and distributed messaging solution that supports both publish-subscribe and queue models. With features like multi-tenancy and a streamlined API, Pulsar enables organizations to efficiently implement real-time data processing.
Use this profile to understand the building block briefly, place it in the model, and open related building blocks.
Technical building block: can be automated, integrated, or operated.
Concrete cog in the system that works inside larger relationships.
Apache Pulsar is a distributed open-source platform for messaging and event streaming with durable topics and multiple subscription models.
Pulsar grew from the need to operate messaging and streaming reliably at high data volumes, across many tenants, and over increasing geographic distribution. The Apache community continues the approach as an openly developed project.
Producers write messages to topics. Pulsar retains them and delivers them to consumers through subscriptions; subscription types determine whether messages are shared, individually tracked, or processed together. Brokers handle access, while persistent storage and replication protect the data.
A topic groups ordered messages for a business or technical event channel.
A subscription defines how consumers receive messages and track progress.
Durable storage enables delayed reading and replay.
Separate tenants and namespaces organize resources and responsibilities.
Pulsar fits event-driven systems, high message volumes, and applications with different consumer and retention requirements. Operations and architecture must consider storage, replication, delivery guarantees, and cluster complexity together.
Where this building block is located in the topic model.
No structure path available.
Explore how this building block connects to concepts, methods, technologies, and tools.
These sources establish the term and its professional meaning.
All direct connections of the current building block in a compact text view.
This classification shows where the building block typically matters, how demanding it is, and what kind of impact it has in the model.
The level within the organization (enterprise, domain, team) at which the AssetBlock is applied.