forked from DiceDB/dice
-
Notifications
You must be signed in to change notification settings - Fork 0
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
- Loading branch information
1 parent
a049d33
commit 0d92ed0
Showing
1 changed file
with
37 additions
and
6 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -1,10 +1,41 @@ | ||
# Roadmap | ||
|
||
- [ ] WAL - persistence and restoration | ||
- [ ] 50% Redis compatability | ||
- [ ] No downtime replica creation | ||
- [ ] Replication lag of < 1 sec at peak | ||
- [ ] Support for Namespaces | ||
- [ ] Support for ACL | ||
As of today, DiceDB consists of four primary pods, each focusing on a critical aspect of the system. | ||
These pods are: | ||
|
||
- Database Engine | ||
- HA, Scale, and Fault Tolerance | ||
- Developer Experience | ||
- Observability and 3P Integrations | ||
|
||
Each pod will drive one or more active macro features or initiatives, with the entire | ||
community collaborating to achieve these goals. Below is an overview of the active | ||
items in each pod: | ||
|
||
## Database Engine | ||
|
||
> Focused on enhancing the core database capabilities, such as supported data structures and performance optimizations. | ||
1. Support for Vectors | ||
2. I/O Optimizations | ||
|
||
## HA, Scale, and Fault Tolerance | ||
|
||
> Aiming to scale DiceDB beyond a single machine and ensure resilience. | ||
1. Replication | ||
2. Snapshots | ||
|
||
## Developer Experience | ||
|
||
> Focused on tools and interfaces like documentation, SDKs, CLI, Playground, and Console to enhance developer productivity. | ||
1. Command search in Playground | ||
|
||
## Observability and 3P Integrations | ||
|
||
> Enhancing monitoring and integration capabilities for better observability and seamless third-party tooling support. | ||
1. DiceDB observability through Prometheus | ||
|
||
> This is not an exhaustive list, Please refer to the [GitHub issues](https://github.com/DiceDB/dice/issues) to find the granular items that are being worked upon. |