| commit | 3ca7408cebfd30a64e1145e847203692bad9824c | [log] [tgz] |
|---|---|---|
| author | Gao Hongtao <hanahmily@gmail.com> | Fri Sep 26 11:22:24 2025 +0800 |
| committer | GitHub <noreply@github.com> | Fri Sep 26 11:22:24 2025 +0800 |
| tree | 4501f7ac1d2d026368a48208bbe542e14beca133 | |
| parent | 8e8f0fab8fd91fe46f3db95459b6435924bb91a5 [diff] |
Refactor mergeBlocks function to simplify block handling (#792)
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.
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.
Request to join SkyWalking slack mail to the mail list(dev@skywalking.apache.org), we will invite you in.[CN] Request to join SkyWalking slack mail to the mail list(dev@skywalking.apache.org), we will invite you in.For developers who want to contribute to this project, see the Contribution Guide.