Installer apache-pulsar avec Homebrew, chocolatey, Nix, scoop, winget

Liens du projet

• Page d'accueil
• Dépôt
• Docs amont
• Page du gestionnaire de paquets

Commandes et alias

• bookkeeper
• function-localrunner
• pulsar
• pulsar-admin
• pulsar-client
• pulsar-daemon
• pulsar-managed-ledger-admin
• pulsar-perf
• pulsar-shell

Historique du projet

Pulsar was originally built at Yahoo for large-scale, multi-tenant messaging. ASF's 2018 graduation announcement says Pulsar launched at Yahoo in 2015, was submitted to the Apache Incubator in June 2017, and then graduated as an Apache top-level project in September 2018.

The architecture separated serving from storage: Pulsar brokers handle topics and clients, while Apache BookKeeper stores ledgers. That split matters operationally because the package ships both Pulsar and BookKeeper command-line entry points.

As the project evolved, Pulsar broadened from a pub-sub broker into a messaging and streaming platform with functions, connectors, tiered storage, schema support, SQL integrations, and tooling around administration and benchmarking.

Historique d'adoption

Pulsar's adoption history is rooted in high-throughput, multi-tenant messaging use cases where operators want durable streams, geo-replication, and independent scaling of brokers and storage. The official documentation presents it as cloud-native distributed messaging and streaming.

The supplied package data shows distribution through Homebrew, Chocolatey, Nix, and Scoop, which is a useful sign of cross-platform developer demand. Homebrew exposes many executables, including `pulsar`, `pulsar-admin`, `pulsar-client`, `pulsar-perf`, and BookKeeper tools.

Modes d'utilisation

Package users commonly install Pulsar to run local standalone clusters, administer tenants/namespaces/topics, test producers and consumers, benchmark message throughput, or develop Pulsar Functions and connectors.

The config layout is conventional for a server package: broker, client, BookKeeper, and functions worker configuration files live under `$PULSAR_HOME/conf`, which keeps command-line experiments close to production deployment concepts.

Pourquoi les passionnés de paquets s'y intéressent

Pulsar is package-nerd interesting because a single formula installs a distributed system with several operational personalities: broker, admin shell, client, storage service, performance tester, and function runtime.

It also sits in the same mental drawer as Kafka, BookKeeper, ZooKeeper-era infrastructure, and cloud-native stream processors, so packagers need to care about Java runtimes, scripts, config directories, and bundled service tooling.

Chronologie

• 2015: Pulsar launches at Yahoo.
• 2017: Pulsar is submitted to the Apache Incubator in June.
• 2018: Pulsar graduates as an Apache top-level project in September.
• 2020s: The project expands its streaming, functions, connector, and cloud-native operations story.

Related projects

• Apache BookKeeper provides the ledger storage layer used by Pulsar.
• Apache ZooKeeper has historically been used for cluster metadata coordination in Pulsar deployments.
• Apache Kafka is the common comparison point for messaging and streaming users evaluating Pulsar.

Sources

• https://github.com/apache/pulsar
• https://news.apache.org/foundation/entry/the-apache-software-foundation-announces39
• https://pulsar.apache.org/
• https://pulsar.apache.org/docs
• source_facts.executables
• source_facts.package-manager