Softwr

Databases · head to head

Apache Pulsar vs Valkey

Apache Pulsar logo

Apache Pulsar

Databases

Cloud-native messaging and streaming with separated storage

From
Free
Rated
-
Full reviewWebsite
Valkey logo

Valkey

Databases

Open-source in-memory data store forked from Redis

From
Free
Rated
-
Full reviewWebsite

The short version

  • Each has a real cost: Apache Pulsar more components than Kafka: brokers, BookKeeper and ZooKeeper each need operating; Valkey younger project, so its track record is short even though the codebase is not
  • They diverge on capability: Apache Pulsar covers Separated storage, Valkey covers Redis-compatible.

Where they differ

Only the attributes on which Apache Pulsar and Valkey actually diverge.

Attributes where Apache Pulsar and Valkey differ
AttributeApache PulsarValkey
Pricing modelOpen source, no licence feeOpen source, no licence fee; managed cloud billed separately
PlatformsLinux, Docker, Kubernetes, Self-hostedLinux, macOS, Docker, Self-hosted

Identical on both: starting price (Free), free tier (Yes), user rating (Not yet rated), category (Databases).

What each one covers

Drawn from each product's published feature list. An absence here means we hold no record of it - not that the product lacks it.

Only in Apache Pulsar

  • Separated storage
  • Queuing and streaming
  • Built-in multi-tenancy
  • Geo-replication

Only in Valkey

  • Redis-compatible
  • BSD licensed
  • Rich data structures
  • Replication and persistence

What people use each for

The jobs each tool is most often brought in to do.

Apache Pulsar

  • Platforms needing both work queues and replayable streams without running two systemsnot Valkey
  • Multi-tenant messaging where isolation between teams is a requirementnot Valkey
  • Deployments where storage and traffic grow at genuinely different ratesnot Valkey

Valkey

  • Continuing on a permissively licensed in-memory store after the Redis licence changenot Apache Pulsar
  • Caching and session storage where a foundation-governed project is a procurement requirementnot Apache Pulsar
  • Migrating from Redis without rewriting application codenot Apache Pulsar

Where each one falls short

Documented limitations, not opinions. Every one is a constraint you would hit in normal use.

Apache Pulsar

  • More components than Kafka: brokers, BookKeeper and ZooKeeper each need operating
  • Correspondingly harder to run well, and the expertise is rarer than Kafka expertise
  • A much smaller ecosystem of connectors, tooling and hiring pool than Kafka
  • The architectural advantages only pay off at a scale most deployments never reach

Valkey

  • Younger project, so its track record is short even though the codebase is not
  • Divergence from Redis grows over time, so compatibility is strongest near the fork point and weakens as both evolve
  • Ecosystem tooling and documentation still frequently assume Redis, leaving translation work

Pricing, plan by plan

Apache Pulsar

Free
  • Apache PulsarFree
    • Full functionality
    • No usage limits
    • Community support

Valkey

Free
  • ValkeyFree
    • Full functionality
    • Self-hosted
    • No usage limits

Which should you pick?

Choose Apache Pulsar if

  • You need separated storage.
  • You want to start without paying.
  • You work on Linux, Docker, Kubernetes, Self-hosted.
  • You also want queuing and streaming.
Apache Pulsar review

Choose Valkey if

  • You need redis-compatible.
  • You want to start without paying.
  • You work on Linux, macOS, Docker, Self-hosted.
  • You also want bsd licensed.
Valkey review

Questions people ask

Is Apache Pulsar or Valkey better?
Neither clearly leads. Apache Pulsar starts at Free and Valkey at Free, and user ratings are close enough to be indistinguishable. Choose on capability and platform support.
Which is cheaper, Apache Pulsar or Valkey?
Apache Pulsar starts at Free and Valkey at Free.
Does Apache Pulsar or Valkey run on more platforms?
Apache Pulsar runs on Linux, Docker, Kubernetes, Self-hosted. Valkey runs on Linux, macOS, Docker, Self-hosted.
Can I use Apache Pulsar for free?
Both have a free tier, so you can try either at no cost before committing.
What is Apache Pulsar best used for?
Apache Pulsar is most often used for platforms needing both work queues and replayable streams without running two systems, multi-tenant messaging where isolation between teams is a requirement, deployments where storage and traffic grow at genuinely different rates. Of those, platforms needing both work queues and replayable streams without running two systems and multi-tenant messaging where isolation between teams is a requirement are not what Valkey is typically brought in for.
What can Apache Pulsar do that Valkey cannot?
Apache Pulsar covers Separated storage, Queuing and streaming, Built-in multi-tenancy, Geo-replication. Valkey covers Redis-compatible, BSD licensed, Rich data structures, Replication and persistence.

Answered from the vendors’ own pages

Apache Pulsar: Is Apache Pulsar free?

Yes, open source under the Apache Software Foundation.

Valkey: Is Valkey free?

Yes, BSD-licensed open source under the Linux Foundation.

Apache Pulsar: Pulsar or Kafka?

Pulsar separates storage from compute and covers queuing and streaming in one system. Kafka has a far larger ecosystem and hiring pool. Most teams should have a specific reason before choosing Pulsar.

Valkey: Why does Valkey exist?

Redis changed its licence away from BSD in 2024. Valkey is the community fork continuing under permissive terms, backed by AWS, Google Cloud and Oracle among others.

Apache Pulsar: Why does separated storage matter?

Brokers hold no data, so adding or replacing one requires no rebalancing, and storage can grow without adding serving capacity.

Valkey: Can I switch from Redis to Valkey?

At the fork point it is drop-in compatible with existing clients and data. The further both projects move from that point, the more you should verify the specific features you use.

Share

Related pages

More on Apache Pulsar

More on Valkey

Keep looking

Other head to heads