Last update 2024-04-03
*the next update ETA 2024-05-15 ⏳
Memgraph product team works in 6-week release cycles. Every six weeks, a new release of Memgraph includes all finished features and resolved bug reports. The exact release dates are visible as Due Dates under milestones. There might be bug-fix releases between regular releases, depending on how critical these fixes are for Memgraph's production deployments.
The team is also considering some form of Long-term Support (LTS) structure. If you have specific input about how we should organize around LTS, feel free to reach out or open a new issue under this repo with the exact expectations.
- All
- Every Memgraph repo has a list of issues (standard Github issues). We link all the issues planned to be resolved in the short term under Community Bugs and Incremental Features.
What does Memgraph offer as an engine?
Desired system properties:
- low-latency
- high-throughput
- data-scale
- algo-scale
- feature-rich
- easy-to-use
- easy-to-change
- correct
- efficient
What should I master to tackle my use case using Memgraph?
Graph meisters skills:
- cypher
- indexing
- query-modules
- streams
- triggers
- memory-usage
- backups
- monitoring
- high-availability
- multi-tenancy
- sharding
- enterprise
The best way to advance the journey with Memgraph is through documentation. Feel free to learn more about Memgraph, spin it, or upgrade to the latest version. If you want to dive deep into the code details, memgraph/memgraph is the best place to start!