Decide About SQLite and User UI Preferences

[SAYaghoubnejad]

Problem Statement:

Currently, user preferences are sent to a Zax node via an API call. The node stores these preferences in an SQLite database. However, there is no mechanism for syncing this data across multiple Zax nodes, leading to inconsistencies in distributed environments.

Proposed Solution:

Instead of storing user preferences in a central SQLite database, consider storing them locally in the user's browser. This approach can eliminate the need for synchronization between nodes and simplify the storage mechanism.

[linear]

TECH-64 Decide About SQLite and User UI Preferences

Problem Statement:

Currently, user preferences are sent to a Zax node via an API call. The node stores these preferences in an SQLite database. However, there is no mechanism for syncing this data across multiple Zax nodes, leading to inconsistencies in distributed environments.

Proposed Solution:

Instead of storing user preferences in a central SQLite database, consider storing them locally in the user's browser. This approach can eliminate the need for synchronization between nodes and simplify the storage mechanism.