Closed adamdriscoll closed 1 year ago
Interesting! Can I ask what prompted the move back to LiteDB?
The user developed their instance on LiteDB and then moved to SQL. They had some issues with certain limitations of PSU (primarily the single job queue). Some of their solution depended on caching data on each node and since the job queues are not node specific, this caused a bunch of issues. Because their deployment window is coming up, they'd like to keep some of their SQL data, like app tokens, and move to LiteDB for the time being.
We have this functionality in the backlog but it won't be done in time.
Awesome, thanks for the info!
Summary of the new feature / enhancement
Customer wants to move SQL data to LiteDB
Proposed technical implementation details (optional)
No response