✨The final part of one of our most-loved series just dropped ✨
Some of you have been following as we build a real-time multi-user Kanban board with @couchdb and @sveltejs.
We’ve already covered requirements + manual and automatic conflict resolution. Post 4/4 delves into UI locking and fun features like audit trails.
Check it out: https://neighbourhood.ie/blog/2025/01/15/resource-locking-with-couchdb-and-svelte
@tyler great question! This tutorial is less “here’s what we’re building in three steps” and more “here are three ways to achieve a goal, let’s explore trade-offs of each.”
In the series, locking is the last thing we explore to prevent conflicts and ensure no one’s data is overwritten. Not all conflicts are equal. Locking solves for some cases automatic resolution can’t catch, but also introduces complexity and adds limitations to the offline capabilities of CouchDB.
The various resolution methods work together. E.g., in a forced reload scenario, trying to save changes to a card that has meanwhile been deleted could make for a jarring experience, so our manual resolution UI would take care of this one.