Logseqs database version

The Logseq team has decided to develop a database version to overcome the current performance issues with Markdown files and to create a more stable, powerful and user-friendly note-taking solution.

The problems with Markdown files #

Logseq has established itself as a powerful tool for organising notes and knowledge, especially in combination with Markdown files. But the current version has some limitations:

• Real-time collaboration: Building real-time collaboration based on Markdown files is a challenge. Adding a new block requires a complete rewrite of the file. And renaming a page, for example, updates all referencing files. This complicates collaboration.
• Data structure: Compared to a database, Markdown files lack structured data support. Functions such as persistent IDs, time stamps and complex queries can only be implemented to a limited extent or not at all. This makes it difficult to organise and manage large collections of notes.

Requirements for the database #

Here are some of the key objectives for the database version:

• Stability and data security: The new version should be more stable and improve data security. Reliable undo/redo functions will ensure that you can edit your work without worry.
• Performance: Speed is a central concern. The database version should enable much faster access to the notes.

Challenges during implementation #

The development of a new database version is a complex endeavour that involves several challenges:

• Cross-platform access: The database should be accessible on different platforms such as web, electron and mobile devices.
• Scalability: It must be able to handle large amounts of data and easily support up to 50,000 pages.
• Data security: Your data should be secure.
• Offline functionality: RTC should also work offline to ensure that you can work with your notes at any time.
• Local control: The local-first approach ensures that users have full control over their data.
• End-to-end encryption: Privacy is of utmost importance, therefore RTC is implemented with end-to-end encryption to ensure user privacy.

Conclusion #

The Logseq team is working exclusively on the realisation of the database version. However, development is progressing more slowly than planned. So we will have to be patient. You can take a look at an early alpha version here.