Correction: This blog is not about Apache Pulsar 3.0
Tags: pulsar-ngThere have been various discussions on the Pulsar dev mailing list about plans for future Pulsar versions.
It’s up to the Apache Pulsar community to decide what Pulsar 3.0 contains eventually. I understand that many might get confused about Pulsar 3.0 plans if that is called out before actual decisions are made. All future content in this blog post series will be decoupled from Pulsar 3.0 because of that reason.
Related Posts
- Scalable distributed system principles in the context of redesigning Apache Pulsar's metadata solution
- Rearchitecting Apache Pulsar to handle 100 million topics, Part 4
- Rearchitecting Apache Pulsar to handle 100 million topics, Part 3
- Rearchitecting Apache Pulsar to handle 100 million topics, Part 2
- Rearchitecting Apache Pulsar to handle 100 million topics, Part 1
- A critical view of Pulsar's Metadata store abstraction
- Pulsar's namespace bundle centric architecture limits future options
- Pulsar's high availability promise and its blind spot
- How do you define high availability in your event driven system?
- Possible worlds for Apache Pulsar 3.0 and making that actual