← Templates · Databases
AP
Apache Pulsar
CommunityCloud-native, multi-tenant pub/sub platform with built-in geo-replication and tiered storage — a Kafka alternative.
| Runs | apachepulsar/pulsar:4.2.5 |
|---|---|
| Stack | jvm |
| Provisioned for it | Nothing, it's self-contained |
| Verified | Not yet |
Why deploy on Railyard
Railyard runs it standalone on a server you already pay for — no addons to provision, with zero-downtime deploys and scaling still included.
Deploying Apache Pulsar is one piece of a bigger stack you can keep building — add a database, a worker, a cache, or another app, all on the same servers you already pay for.
Good for
- Multi-tenant pub/sub messaging with built-in geo-replication
- An alternative to Kafka when you need native multi-tenancy or tiered/long-term storage of topics
- Queue and streaming semantics on the same platform (shared vs. exclusive subscriptions)
Good to know
- Standalone mode bundles ZooKeeper, BookKeeper, and the broker in one process — it's meant for a single team's workload, not a clustered production deployment
- Needs real memory headroom — Pulsar's own docs recommend at least 2-4GB free for standalone mode; undersized servers will see the broker get OOM-killed
- The broker port (6650, binary protocol) isn't this app's public port — only the HTTP admin/REST port (8080) is. Point Pulsar clients at this app's private domain on 6650