Release Apache SkyWalking BanyanDB 0.1.0
Add NOTICE to binary package and fix some typo (#128)

* Add NOTICE to binary package and fix some typo
* Update CONTRIBUTING.md

Signed-off-by: Gao Hongtao <hanahmily@gmail.com>
9 files changed
tree: 02bac9a779a2811e971f98791b9409cc9918bc8c
  1. .github/
  2. api/
  3. assets/
  4. banyand/
  5. dist/
  6. docs/
  7. pkg/
  8. scripts/
  9. test/
  10. .asf.yaml
  11. .gitignore
  12. .licenserc.yaml
  13. CHANGES.md
  14. CONTRIBUTING.md
  15. go.mod
  16. go.sum
  17. golangci.yml
  18. LICENSE
  19. Makefile
  20. NOTICE
  21. README.md
README.md

BanyanDB

BanyanDB, as an observability database, aims to ingest, analyze and store Metrics, Tracing and Logging data. It's designed to handle observability data generated by observability platform and APM system, like Apache SkyWalking etc.

Introduction

BanyanDB, as an observability database, aims to ingest, analyze and store Metrics, Tracing, and Logging data. It's designed to handle observability data generated by Apache SkyWalking. Before BanyanDB emerges, the Databases that SkyWalking adopted are not ideal for the APM data model, especially for saving tracing and logging data. Consequently, There’s room to improve the performance and resource usage based on the nature of SkyWalking data patterns.

The database research community usually uses RUM conjecture to describe how a database access data. In this talk, I will share the details about BanyanDB based on this conjecture, explaining why BanyanDB is more effective and reliable than other storage layers.

Documents

Documents

Contributing

For developers who want to contribute to this project, see Contribution Guide

License

Apache 2.0 License.