Ross ROSS = Recommend OSS · open-source software intelligence for agents

apache/pulsar

Apache Pulsar - distributed pub-sub messaging system observed · 2026-08-28

github.com/apache/pulsar · homepage · Java · Apache-2.0 (permissive) observed · 2026-08-28

Health v2 · maintenance only

98/100

  • Activity 99
  • Release rhythm 96
  • Longevity 100
How is this computed?

round(0.45*activity + 0.35*rhythm + 0.20*longevity); archived -> min(score, 10) — computed 2026-09-03. Adoption (stars, forks) is never an input.

  • gap_med: 0
  • age_days: 3718
  • days_rel: 30
  • days_push: 7
  • n_releases_24m: 42

Full methodology

Adoption not part of the score

15315 stars · 3748 forks observed · 2026-08-28

What it is AI-extracted, prompt v1, taxonomy v1, 2026-08-29, confidence not recorded

Apache Pulsar is a cloud-native, distributed pub-sub messaging and streaming platform originally developed at Yahoo and now a top-level Apache project. It combines flexible queuing and streaming semantics with multi-tenancy, geo-replication, tiered storage, and a layered architecture that scales horizontally to millions of topics and messages per second.

Use cases

  • build a distributed work queue with guaranteed message delivery
  • stream events between microservices at low latency
  • replicate messages across geographic regions with automatic failover
  • run a multi-tenant messaging cluster for an entire organization
  • process event streams with Pulsar Functions
  • offload aged message data to S3 or GCS with tiered storage
  • consume messages individually or as ordered streams

When to choose

  • you need both queuing and streaming semantics in one platform
  • you require multi-tenancy, quotas, and access control on a shared cluster
  • you need geo-replication and cluster-level failover out of the box
  • you need to scale to hundreds of nodes and a million topics without data reshuffling
  • you want official clients for Java, Go, Python, C++, C#, and Node.js

When to avoid

  • you need a lightweight single-node message broker for a small app
  • your team cannot operate a multi-component system (broker, BookKeeper, ZooKeeper)
  • you are already deeply invested in Kafka's ecosystem and tooling
  • you only need simple point-to-point RPC without messaging guarantees

Facets

service · maturity stable

message-queue streaming rpc auth authorization microservices big-data backend cloud-computing jvm cross-platform self-hosted cloud pubsub event-streaming geo-replication multi-tenancy apache bookkeeper tiered-storage transactions messaging real-time docker kubernetes linux macos

6 sources

Member repositories

RepositoryRoleHealth v2
apache/pulsarmain98

For agents

markdown · JSON · MCP: product_card(name="apache/pulsar")

Data as of 2026-08-30T08:39:29.467469+00:00 · Report a problem