noms
offix
Our great sponsors
noms | offix | |
---|---|---|
11 | 2 | |
7,502 | 771 | |
- | - | |
1.9 | 0.0 | |
over 2 years ago | about 1 year ago | |
Go | TypeScript | |
Apache License 2.0 | Apache License 2.0 |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
noms
-
How Dolt Stores Table Data
This is from 2022. It is based on Noms [1], which is no longer maintained (they forked it).
I think the Noms doc linked from this article [2] is clearer than the article itself. That said I sill cannot turn my head around to grasp how this entire thing work tbh. I hope they wrote a peer reviewed paper to serve the audience better.
[1] https://github.com/attic-labs/
[2] https://github.com/attic-labs/noms/blob/master/doc/intro.md#...
-
I was wrong. CRDTs are the future
I am. But i know very little about CRDTs lol, so we'll see how that goes. I'm interested in converting some immutable, local-first data warehouse tooling i enjoy to a CRDT version. Prior it was more.. Git-like. Basically just Git with data structures inspired-massively from Noms[1].
The thing i've found most interesting is it appears[2] that CRDT backends need to expose CRDT flavored types to users. Which is to say how i'm writing this combines the notion of a type, say `[i32]` with how you want the merges to work. CRDT works great but based on my amateur-hour researching on the subject i don't feel you can write a single CRDT merge strategy for a single data type ala `[i32]` and have it be always correct. Applications need to indicate enough context on what makes sense for a given data type.
So yea, i agree with you. I'm interested in making a database-like thing, backed by CRDTs, but i also have seen very few general purpose implementations with CRDTs. It feels like i'm breaking "new ground", while having no idea what i'm doing and having no intention of being an actual researcher here. I'm just making apps i enjoy heh.
[1]: https://github.com/attic-labs/noms
- Building a decentralized database
-
Picking low-hanging memory usage bugs of an open source database
Most of the changes are in the noms package which used to live in a separate repo (https://github.com/attic-labs/noms), but Dolt has since adopted them.
-
Downsides of Offline First
Not much more to say other than Noms was my favorite project (https://github.com/attic-labs/noms) for a while until acquisition and the engineers are now the ones behind Replicache (https://replicache.dev/).
I think this is going to be the next "Realm" that works everywhere.
- calling Format() on a time struct in a golang program changes the default Location's timezone information in the rest of the program
-
Steps to build Database System from sratch?
The storage layer based on Noms: https://github.com/attic-labs/noms
- Noms: The versioned, forkable, syncable database
-
Dolt is Git for Data: a SQL database that you can fork, clone, branch, merge
Noms might be what you’re looking for (https://github.com/attic-labs/noms). Dolt is actually a fork of Noms.
-
CondensationDB: Build secure and collaborative apps [open-source]
People that are interested in a similar feature set should check out https://github.com/attic-labs/noms and the SQL fork of Noms, https://github.com/dolthub/dolt
offix
-
Downsides of Offline First
Yeah,I'm trying to implement an electron offline first app that syncs, there seems to readymade solution.
Stuff like https://github.com/aerogear/offix seem to be in the right direction of what I'm looking for but not nearly mature enough.
I don't want to pu to much effort on the app so I would like something more or less ready made, preferably with graphql apis.
Any suggestions welcome.
-
Is GraphQL a wrong choice for offline-first apps?
I ended up with Offix and had to do optimistic cache handling, and I wrote up my experiences in a GitHub ticket on their repo with code as guidance for others. https://github.com/aerogear/offix/issues/715
What are some alternatives?
rqlite - The lightweight, distributed relational database built on SQLite.
howtographql - The Fullstack Tutorial for GraphQL
dat - Go Postgres Data Access Toolkit
destreamer - Save Microsoft Stream videos for offline enjoyment.
dolt - Dolt – Git for Data
apollo-log - A logging extension for the Apollo GraphQL Server
sql-migrate - SQL schema migration tool for Go.
absurd-sql - sqlite3 in ur indexeddb (hopefully a better backend soon)
skeema - Declarative pure-SQL schema management for MySQL and MariaDB
crdt-example-app - A full implementation of CRDTs using hybrid logical clocks and a demo app that uses it
cockroach - CockroachDB - the open source, cloud-native distributed SQL database.
cashew - 🐿 A flexible and straightforward library that caches HTTP requests in Angular