Storing #RDF or #LinkedData is the easy part (I am working on #activitypub client, so everything is JSON-LD anyway), but as soon as I need to formulate queries like "Give me list of the activities from all the actors who are on the following collection of my user, sorted by published/updated date", the amount of data mangling that I need to do is already making me think "ok, why don't I just push all of this to sqlite?"
Oh _no_
in #CouchDB, Mango querying does not mix with using "" as document key.
"One or more conditions is missing a field name."
Stressful start to the year?
You have one less worry with #CouchDB
Our latest article covers @couchdb’s #checksums feature: a built-in safeguard that helps protect your data from the impact of ever-dreaded disk corruption.
It’s just one of the features that makes CouchDB your data’s safe place.
Full post on our blog: https://neighbourhood.ie/blog/2025/01/22/how-couchdb-prevents-data-corruption-checksums
We published a four part series about how to build a real-time multi-user Kanban board with @couchdb and @sveltejs
Its is complete with code for all steps, so it’s not just a draw-the-rest-of-the-owl tutorial:
1. Setup, intro, first steps: https://neighbourhood.ie/blog/2024/12/05/realtime-multiuser-kanban-board-with-couchdb
2. Automatic Conflict Resolution: https://neighbourhood.ie/blog/2024/12/11/automatic-conflict-resolution
3. Manual Conflict Resolution: https://neighbourhood.ie/blog/2024/12/18/manual-conflict-resolution-with-couchdb-and-svelte
4. Avoiding Conflicts with Resource Locking: https://neighbourhood.ie/blog/2025/01/15/resource-locking-with-couchdb-and-svelte
@gilgwath It would be best to have the #database (and data) to run completely in the same RAM that the host CPU is on. Basically the storage and the compute need to occur on the same node. Not everyone has enough RAM to do this. #Longhorn is a good technology to enable the storage part.
#k8s
#PostgreSQL
#MariaDB
#SQL
#NoSQL
#MongoDB
#ApacheCassandra
#CouchDB
Pārmērīgi tehnisks saturs
Based on the amount and subtlety of wrappers I'm writing for my #CouchDB library, I think we need more of those.
Yeah, you can just call it with HTTP directly. But you're going to stumble into things.
.0 releases get more press, but it wasn't the right thing to do, and #CouchDB chose the better path. Kudos to Apache CouchDB for sacrificing a marketing win for a *user* win. https://blog.couchdb.org/2024/09/27/3-4-1/
Beyond Tellerrand #btconf is in Berlin! In-person conferences are a thing again, and we’re really happy to connect with the #JS and #CouchDB communities face to face, collect stickers and share inspiring vibes.
Neighbourhoodies’ @janl is around — don’t miss saying hi!
If you weren’t able to make it, catch you in the comments soon. Subscribe so you don’t miss the talks when they’re up: https://www.youtube.com/btconf
Time is running out to download our Focus Guide: Open Source Databases. Get up to speed on the open source database ecosystem and learn which solution could be right for your organization. This focus guide is available free for a limited time thanks to our partner Percona
https://mailchi.mp/admin-magazine.com/open-source-databases
#OpenSource #database #FOSS #Percona #PostgreSQL #MySQL #MariaDB #CouchDB
Sincronizar Obsidian n
sincronizar #obisidian en #linux y #android utilizando #webdav #couchdb o #minio para poder trabajar en cualquier dispositivo y en movilidad
Escucha: https://atareao.es/podcast/sincronizar-obsidian/
Feed: https://atareao.es/mp3-feed/
For 12 years already, I've been on/off experimenting (and prototyping) to create a compendium & knowledge graph about computational & generative art, the different movements/genres/mediums (e.g. architecture, design, visual art, audio/music, sculpture, kinetic/motion, film/animation, text etc.), influences, definitions/references, people (artists, curators, writers, thinkers), collectives, organizations (foundations, galleries, museums), exhibitions/festivals, tools & tool makers, common techniques used, art platforms — everything tagged and also supporting to browse by time (centuries & decades, currently starting ~1600) and region...
Attached are some screenshots of my first prototypes from 2011/12 (using #CouchDB, then #neo4j for storage & my own tools for force-directed graph layout) and of the current prototype using #Logseq (https://logseq.com)... The latter is working great for now and feeling, I'm getting somewhere this time, also because I have to make it work (for work!). This is all still just a beginning, hundreds of more people, orgs, projects & references to import and re-check from older versions. The current contents are _very_ biased to my own network/trajectory in/through this space...
Ps. Following up with all the folks & materials I've included already, I'm realizing again and again just how I've been the most naïve and _worst_ person to monetize (mostly not even trying!) my art/contributions... For 20 years I've filed 90% of hundreds of my projects under "experiments", "sketches", "demos", "tutorials" (often also to help illustrate techniques of my open source tools), only to realize (not for the first time) almost everyone else of my old peers has been way less selective and been attaching way more importance to all of their outputs... Maybe one day I will learn, before it's too late...