We build offline capable web applications with @couchdb & @pouchdb — In the past: @greenkeeperio @jsconfeu @berlinjs & @hoodiehq.
Catch tips on our favourite technologies and see what we’re up to: https://neighbourhood.ie/blog
Tried the 🆕 CouchDB Minihosting yet? Want to get an Offline-First environment up-and-running in minutes (not hours)?
Tried the 🆕 CouchDB Minihosting yet? Want to get an Offline-First environment up-and-running in minutes (not hours)?
We’ve put together a demo app tutorial to show off Minihosting with @sveltejs 5, @vite and Pico.css. And @couchdb + @pouchdb, of course!
If you’re curious about the state of Offline-First in 2025, this is it!
Check out the full tutorial: https://neighbourhood.ie/blog/2025/03/26/offline-first-with-couchdb-and-pouchdb-in-2025
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.
@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 final part of one of our most-loved series just dropped ✨
✨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
Coding @couchdb is one thing, but do you have a CouchDB mindset? 🧩
Coding @couchdb is one thing, but do you have a CouchDB mindset? 🧩
We’ve just added 2/4 parts of an in-depth tutorial to our blog: a real-time multi-user Kanban board with CouchDB and @sveltejs.
Spoiler: no server-side code to start. Relaxing, right?
Part 1 covers requirements, challenges and trade-offs. The main challenge? Conflicts!
Core principles to avoid them: Making data granular + updating as few docs as possible
Check it out: https://neighbourhood.ie/blog/2024/12/05/realtime-multiuser-kanban-board-with-couchdb
More on part 2 🧵