LinDB is an open-source Time Series Database which provides high performance, high availability and horizontal scalability.

LinDB stores all monitoring data of ELEME Inc, there is 88TB incremental writes per day and 2.7PB total raw data.

• High performance

  LinDB takes a lot of best practice of TSDB and implements some optimizations based on the characteristics of time series data. Unlike writing a lot of Continuous-Query for InfluxDB, LinDB supports rollup in specific interval automatically after creating the database. Moreover, LinDB is extremely fast for parallel querying and computing of distributed time series data.

• Multi-Active IDCs native

  LinDB is designed to work under a Multi-Active IDCs cloud architecture. The compute layer of LinDB, called brokers, supports efficient Multi-IDCs aggregation query.

• High availability

  LinDB uses the ETCD cluster to ensure the meta-data is highly available and safely stored. In the event of failure, the Multi-channel replication protocol of WAL will avoid the problem of data inconsistency:

  1). Only one person in each replication channel is responsible for the authority of the data, so the conflicts will not happen;

  2). Data reliability is guaranteed: as long as the data that has not been copied in the old leader is not lost, it will be copied to other replication while the old leader is online again;

• Horizontal scalability

  Tags based sharding strategy in LinDB solves the hotspots problem, and is truly horizontally expanded available by simply adding new broker and storage nodes.

• Governance capability of metrics

  To ensure the robustness of the system, LinDB do not assume that users has understood the best practices of using metrics, therefore, LinDB provides the ability of restricting unfriendly user based on metric granularity and tags granularity.

The current develop branch is unstable and is not recommended for production use. LinDB 0.1(what will be the first release version) is currently in the development stage. Additional features will arrive during July, we will translate the JAVA version of LinDB currently used under the production environment to Golang as soon as possible.

Once we implement the final feature and replace the LinDB under production environment with the Golang version, LinDB 0.1.0 will be released. At that point, we will move into the stable phase, our intention is to avoid breaking changes to the API and storage file format.

Contributions are welcomed and greatly appreciated. See CONTRIBUTING for details on submitting patches and the contribution workflow.

Pull requests should be appropriately labeled, and linked to any relevant bug or feature tracking issues. All pull requests will run through Travis-CI. Community contributors should be able to see the outcome of this process by looking at the checks on their PR and fix the build errors.

This project uses the following linters. Failure during the running of any of these tools results in a failed build. Generally, code must be adjusted to satisfy these tools.

• gofmt - Gofmt checks whether code was gofmt-ed. By default this tool runs with -s option to check for code simplification;
• golint - Golint differs from gofmt. Gofmt reformats Go source code, whereas golint prints out style mistakes;
• goimports - Goimports does everything that gofmt does. Additionally it checks unused imports;
• errcheck - Errcheck is a program for checking for unchecked errors in go programs. These unchecked errors can be critical bugs in some cases;
• gocyclo - Computes and checks the cyclomatic complexity of functions;
• maligned - Tool to detect Go structs that would take less memory if their fields were sorted;
• dupl - Tool for code clone detection;
• goconst - Finds repeated strings that could be replaced by a constant;
• gocritic - The most opinionated Go source code linter;

LinDB is under the Apache 2.0 license. See the LICENSE file for details.