Google Git
Sign in
apache / skywalking-banyandb / 23139b99ec2b0be194c3bf4bab140a125001fa0a
commit23139b99ec2b0be194c3bf4bab140a125001fa0a[log] [tgz]
authorachintya <achintya22052000@gmail.com>Fri May 19 13:37:54 2023 +0530
committerGitHub <noreply@github.com>Fri May 19 16:07:54 2023 +0800
tree356263881274ee25fcfc489c9b5fc4e5c7109afe
parentb544c55b0fdad6044e1e14810a11f3a2663550ad [diff]
modified TestGoVersion to check Go CPU architectue (#273)

* modified TestGoVersion to check go cpu architectue

* removed os.exec(go version) with runtime.Version

* added cpu arch check via uintptr

* modified the test message

* updated changes.md
2 files changed
tree: 356263881274ee25fcfc489c9b5fc4e5c7109afe
  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. go.mod
  23. go.sum
  24. LICENSE
  25. Makefile
  26. NOTICE
  27. README.md
  28. 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.