Apache Pulsar VS jetstream

Ingest real-time data from Kafka, Pulsar, or CDC sources like Postgresand MySQL, with built-in support for Debezium.

Apache Pulsar: Pulsar is a distributed messaging platform developed under the Apache Foundation. Its notable features include extremely low latency, support for multi-tenancy, geo-replication across regions, and tiered storage capabilities.

From Apache, there's Pulsar, a distributed pub-sub messaging platform with a flexible messaging model, and an intuitive client API. The latest version brings enhanced Key_Shared subscription implementation, secure Docker runtime based on Alpine Linux and Java 21, rate limiting, enhanced client compatibility, and more. Check out the release notes to read more about all the changes since the last release.

Apache Pulsar is an open-source distributed messaging platform originally developed by Yahoo! It provides a highly scalable solution for messaging and stream processing with robust durability and fault tolerance.

Stream-processing platforms such as Apache Kafka, Apache Pulsar, or Redpanda are specifically engineered to foster event-driven communication in a distributed system and they can be a great choice for developing loosely coupled applications. Stream processing platforms analyze data in motion, offering near-zero latency advantages. For example, consider an alert system for monitoring factory equipment. If a machine's temperature exceeds a certain threshold, a streaming platform can instantly trigger an alert and engineers do timely maintenance.

Edit: Here's a good example of what I'm looking for: https://github.com/apache/pulsar. It is a full application that happens to be deployed (or deployable) with Terraform, and the configuration files are available.

In recent years, it has become apparent that almost no production system is complete without real-time data. This can also be observed through the rise of streaming platforms such as Apache Kafka, Apache Pulsar, Redpanda, and RabbitMQ.

It's colored black on the refreshed Apache Pulsar site. https://pulsar.apache.org/

Sorry, I'm not familiar with this tech so looked up Jetstream and it seems to be archived https://github.com/nats-io/jetstream. Not sure that would be a good endorsement to try to use something that is no longer maintained or am I looking at the wrong one?

Centrifugo can use Nats as PUB/SUB broker. I also tried to use Jetstream to implement Centrifugo history/recovery semantics – unfortunately Jetstream does not fit us very well as streams must be created over a separate call to admin API, and it's not possible to iterate/paginate over Jetstream streams to be suitable to current Centrifugo message history and recovery semantics (I asked about support for this – unfortunately the issue was closed and required API not implemented - https://github.com/nats-io/jetstream/issues/266, suggested solution is far from optimal for our use case).