Google Git
Sign in
apache / skywalking-banyandb / refs/tags/v0.2.0
tagedb81b23dd7813569bd5b7ce1ae5a0fd53b415e4
taggerGao Hongtao <hanahmily@gmail.com>Sun Nov 06 06:19:04 2022 +0000
object566314a3d72299879233e8b66be218df3b73b6e0 
Release Apache SkyWalking BanyanDB 0.2.0
commit566314a3d72299879233e8b66be218df3b73b6e0[log] [tgz]
authorGao Hongtao <hanahmily@gmail.com>Sat Nov 05 22:17:31 2022 +0800
committerGitHub <noreply@github.com>Sat Nov 05 22:17:31 2022 +0800
tree97c0acf8d0ae989f662dc73db8415a2d73c1217e
parent40e6e5956f20d89c125b1e8604aaebcbdc6a028d [diff]
Add data-model.md to explian objectes in API (#198)
4 files changed
tree: 97c0acf8d0ae989f662dc73db8415a2d73c1217e
  1. .github/
  2. api/
  3. assets/
  4. banyand/
  5. bydbctl/
  6. dist/
  7. docs/
  8. pkg/
  9. scripts/
  10. test/
  11. ui/
  12. .air.toml
  13. .asf.yaml
  14. .dockerignore
  15. .gitattributes
  16. .gitignore
  17. .golangci-format.yml
  18. .golangci.yml
  19. .licenserc.yaml
  20. CHANGES.md
  21. CONTRIBUTING.md
  22. deprecated-golangci.yml
  23. go.mod
  24. go.sum
  25. LICENSE
  26. Makefile
  27. NOTICE
  28. README.md
  29. revive.toml
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. BanyanDB combines several access methods to build a comprehensive APM database to balance read cost, update cost, and memory overhead.

Documents

Documents

RoadMap

Client manager

  • [x] gRPC server
  • [x] HTTP server

Distributed manager (v1.0.0)

  • [ ] Sharding
  • [ ] Replication and consistency model
  • [ ] Load balance
  • [ ] Distributed query optimizer
  • [ ] Node discovery
  • [ ] Data queue

Data processor

  • [x] Schema management
  • [x] Time-series abstract layer
  • [x] Stream data processor
  • [x] Measure data processor
  • [x] Property data processor
  • [x] TopNAggregation processor
  • [x] Index processor
  • [x] TTL
  • [x] Cold data processor
  • [ ] WAL (v0.3.0)

Query processor

  • [x] Stream query processor
  • [x] Measure query processor
  • [x] Index reader
  • [x] Streaming pipeline processor(OR and nested querying)
  • [ ] Parallel executor
  • [ ] Cost-based optimizer

Verification

  • [x] E2E with OAP and simulated data
  • [ ] E2E with showcases, agents and OAP (v0.3.0)
  • [x] Space utilization rate
  • [ ] Leading and trailing zero (v0.4.0)
  • [ ] Stability (v0.3.0)
  • [ ] Crash recovery (v0.3.0)
  • [ ] Performance

Tools

  • [x] Command-line
  • [ ] Webapp (v0.4.0)

Contributing

For developers who want to contribute to this project, see the Contribution Guide](CONTRIBUTING.md)

License

Apache 2.0 License.