[ ] Creation of simplified (master-slave) but a more stable version of distributed storage based on new architecture.
User API
[ ] Implementation of security on the property level and record level.
Storage engine:
[ ] Making Lucene indexes durable (right now we rebuild them after the crash, that causes problems not only after the crash but during restore from incremental backups)
[x] Encryption of database on file level.
[ ] Implementation of physiological logging to increase overall write throughput.
[ ] Increasing speed of graph queries for the data which are not cached in memory for several times.
[ ] Fixing slowdown of indexes on writes once they do not fit in memory. That is a common problem of all B-Tree based indexes.
[ ] Fixing of a 1-sec gap during which data can be lost in case of a server crash
We’re sharing the information on this roadmap to outline OrientDB team plans. All information provided on this site is provided for INFORMATIONAL PURPOSES ONLY, is general in nature, and is not intended to and should not be relied upon or construed as a binding commitment. OrientDB team makes no guarantees of any kind regarding the information herein.
Please do not rely on this information in making decisions, as the development, release and timing of any products, features or functionality shall be made in OrientDB team's sole discretion, and is subject to change.