Apache BookKeeper - a scalable, fault tolerant and low latency storage service optimized for append-only workloads

Clone this repo:
  1. 45f7a92 Fix documentation terminology and method usage (#4617) by Xiangying Meng · 3 days ago master
  2. 4e6583d chore: cleanup useless arg from Dockerfile (#4634) by Zixuan Liu · 5 days ago
  3. 3bb2401 [improve][build] solve the dead links found in md (#4637) by StevenLuMT · 5 days ago
  4. 487be97 docs: add news about 4.16.7 and 4.17.2 release (#4635) by StevenLuMT · 9 days ago
  5. f2f6f56 Update latest docker image version to 4.17.2 (#4633) by StevenLuMT · 9 days ago

Maven Central

Apache BookKeeper

Apache BookKeeper is a scalable, fault-tolerant and low latency storage service optimized for append-only workloads.

It is suitable for being used in following scenarios:

  • WAL (Write-Ahead-Logging), e.g. HDFS NameNode, Pravega.
  • Message Store, e.g. Apache Pulsar.
  • Offset/Cursor Store, e.g. Apache Pulsar.
  • Object/Blob Store, e.g. storing state machine snapshots.

Get Started

  • Checkout the project website.
  • Concepts: Start with the basic concepts of Apache BookKeeper. This will help you to fully understand the other parts of the documentation.
  • Follow the Installation guide to set up BookKeeper.

Documentation

Please visit the Documentation from the project website for more information.

Get In Touch

Report a Bug

For filing bugs, suggesting improvements, or requesting new features, help us out by opening a GitHub issue.

Need Help?

Subscribe or mail the user@bookkeeper.apache.org list - Ask questions, find answers, and also help other users.

Subscribe or mail the dev@bookkeeper.apache.org list - Join development discussions, propose new ideas and connect with contributors.

Join us on Slack - This is the most immediate way to connect with Apache BookKeeper committers and contributors.

Contributing

We feel that a welcoming open community is important and welcome contributions.

Contributing Code

  1. See our installation guide to get your local environment setup.

  2. Take a look at our open issues: GitHub Issues.

  3. Review our coding style and follow our pull requests to learn more about our conventions.

  4. Make your changes according to our contributing guide