I’m currently self-hosting on Postgres with Typesense on the side for search.
Today I came across the deprecation notice that Vikunja is moving from Typesense to ParadeDB.
Reading the ParadeDB docs, I noticed this call-out on the Guarantees page:
ParadeDB Community does not write to the WAL, and therefore does not guarantee durability in the face of crashes. For production use cases that require full durability, ParadeDB Enterprise — a closed-source fork of ParadeDB for enterprise customers — includes full WAL integration.
It seems like my options as a self-hoster with ParadeDB are to either use community edition and not have data durability in the event of a crash, or pay for Enterprise ParadeDB.
Is this correct? Or are there plans for another option for Vikunja self-hosters to retain WAL support?
1 Like
Below are my assumptions based on experience with similar systems.
It’s not data that gets lost, only indexes (data from DB preloaded into memory).
Worst case ParadeDB will notice the crash and re-index everything - how long depends on how much data you have. Not something ridiculous though.
I would imagine right after the crash your search queries are going to take longer to execute because of “slow” PG DB reads vs fast memory reads.
No need to invest in pro fork unless you really don’t want laggy system on rare occasions.
P.S. thanks for sharing the post - I wouldn’t know about this otherwise. Would be nice if such updates could be posted on this forum not only for visibility, but also for discussion.
Thanks for the response!
Based on what you’re saying and after reading some more documentation, it sounds like the “core” functionality of Postgres is preserved and that ParadeDB is just adding in the pg_search extension, which is the piece that the docs were referring to that doesn’t use the WAL?
That should be fine then.