canonical/dqlite

Embeddable, replicated and fault-tolerant SQL engine.

View on GitHub ↗Jump to charts ↓

Summary Information

Updated 30 minutes ago
Type:Library / SDKCategory(s):Relational & SQL DatabasesDatabases & Storage
Added to GitGenius on September 15th, 2026
Created on May 24th, 2017
Open Issues & Pull Requests: 48 (+0)
GitHub issues: Enabled
Number of forks: 255
Total Stargazers: 4,383 (+0)
Total Subscribers: 75 (+0)

Repository Insights (GitGenius)

Median issue/PR response: 9.7 days
Mean response time: 94.0 days
90th percentile: 332.1 days
Tracked items: 45

Most active contributors

Sign in to see contributor activity.

Charts & Analytics

Fetching additional details & charts...

Issue Activity (beta)

Open issues: 10
New in 7 days: 0
Closed in 7 days: 0
Avg open age: 347 days
Stale 30+ days: 7
Stale 90+ days: 6

Recent activity

Opened in 7 days: 0
Closed in 7 days: 0
Comments in 7 days: 0
Events in 7 days: 0

Top labels

  • Feature (13)
  • Bug (3)
  • transferred-from-raft (3)
  • Incomplete (1)

Most active issues this week

No issue events were indexed in the last 7 days.

Detailed Description

Dqlite is an embeddable, replicated SQL database engine that extends SQLite with distributed consensus capabilities.

Dqlite solves the problem of running SQL workloads across multiple nodes while maintaining consistency and fault tolerance. It embeds SQLite as its query engine and layers the Raft consensus algorithm on top to coordinate state across a cluster. This approach allows applications to use familiar SQL semantics while gaining automatic replication, leader election, and recovery from node failures without requiring a separate database server.

Dqlite suits projects that need a lightweight, embedded database with built-in clustering rather than a standalone server. It works well for applications running on multiple machines that require strong consistency guarantees and can tolerate the latency overhead of consensus. Teams should adopt it when they want to avoid the complexity of managing a separate database cluster but still need fault tolerance beyond what a single SQLite instance provides. The tool is particularly valuable for systems where embedding the database directly into the application process reduces operational burden.

The project maintains active development with regular commits addressing bug fixes and feature improvements. Pull requests receive timely review and feedback from maintainers. The codebase shows consistent attention to test coverage and stability. Documentation is kept current alongside code changes. The maintainers respond to issues and engage with the community on technical questions about usage and design decisions.