Graph-Based Ceramics
The article discusses managing ceramic glazes, introducing a custom app. It compares Firebase and Supabase databases, opting for Supabase's better data modeling. Instant database is explored for a hybrid solution.
Read original article
The article discusses the challenges of managing ceramic glazes and combinations, leading to the creation of a custom app. The author explores different database options to store and retrieve data efficiently. Initially considering Firebase for its ease of use but realizing its limitations in handling relational data, the author opts for Supabase, a PostgreSQL-based solution, for better data modeling capabilities. However, Supabase lacks some features like optimistic updates and offline support that Firebase offers. The author then explores Instant, a graph-based database, as a potential solution that combines the speed of Firebase with the relational capabilities of Supabase. Instant's querying language, InstaQL, simplifies data retrieval without the need for complex configurations. The article highlights the ease of creating and querying data in Instant using transactions to establish relationships between objects. Ultimately, the author finds Instant to be a promising option for efficiently managing ceramic data with its graph-based approach.
Related
Show HN: Triplit – Open-source syncing database that runs on server and client
The GitHub URL provides details on `@changesets/cli`, a tool for versioning and publishing code in multi-package and single-package repositories. Full documentation and common questions are accessible in their repository.
Graph-Based Ceramics
The article explores managing ceramic glazes in a kiln and developing an app. It compares Firebase, Supabase, and Instant databases, highlighting Instant's efficiency in handling complex relational data for ceramic management.
Graph-Based Ceramics
The article explores managing ceramic glazes in a kiln and creating an app for this purpose. It compares Firebase and Instant databases, Supabase, Postgres, and InstaQL for efficient data handling.
TinyBase v5: CRDTs for the rest of us
TinyBase is a versatile reactive data store for local-first apps, featuring data listening, synchronization, local storage, and schema support. It offers tools for key-value stores, tabular data, React integration, and complex queries.
5 commentsSurprised to see this on the front page again (hello fellow pottery enthusiasts?), but figured this could be a good chance to address some of the comments from the recent discussion [0] since I missed it last time :P
The most common feedback seemed to be, "this is dumb, just use SQLite", which is definitely valid.
This was actually how I initially started building the app (using SQLite), and it worked pretty well. There were a couple reasons I abandoned this approach though: one, whenever I had to uninstall and reinstall the app, the data would get wiped; two, I still had to deal with migrations and other annoying boilerplate; and three, I wanted to be able to share my results with my friends in a read-only web view.
(That being said, I'm also curious to explore how tools like ElectricSQL [1], PowerSync [2], TinyBase [3], etc. play with SQlite to handle some of these issues. At a glance, it just seemed like these would require more time to setup compared to InstantDB [4].)
Another similar comment that popped up a few times was the idea that if I'm trying to model _relational_ data, it would be ridiculous to use anything other than a _relational_ database.
I think that's fair, but I also think it's fair to say a graph database is also "relational" in some sense, or at least "relationship-centric" [5] :)
Either way, I had a lot of fun with this. And I was definitely optimizing more for speed/scrappiness than for doing it The Right Way, so if anyone has any thoughts on how to build stuff faster, I'd love to hear it!
[0] https://news.ycombinator.com/item?id=40860116
[2] https://www.powersync.com/
[4] https://www.instantdb.com/
[5] https://aws.amazon.com/compare/the-difference-between-graph-...
Lately I hack in firebase and have been interested in trying supabase. I’ll have to add instantdb to my list.
You should productionize this! Get glaze recipes in there too!
Graph-Based Ceramics - https://news.ycombinator.com/item?id=40860116 - July 2024 (17 comments)
Related
Show HN: Triplit – Open-source syncing database that runs on server and client
The GitHub URL provides details on `@changesets/cli`, a tool for versioning and publishing code in multi-package and single-package repositories. Full documentation and common questions are accessible in their repository.
Graph-Based Ceramics
The article explores managing ceramic glazes in a kiln and developing an app. It compares Firebase, Supabase, and Instant databases, highlighting Instant's efficiency in handling complex relational data for ceramic management.
Graph-Based Ceramics
The article explores managing ceramic glazes in a kiln and creating an app for this purpose. It compares Firebase and Instant databases, Supabase, Postgres, and InstaQL for efficient data handling.
TinyBase v5: CRDTs for the rest of us
TinyBase is a versatile reactive data store for local-first apps, featuring data listening, synchronization, local storage, and schema support. It offers tools for key-value stores, tabular data, React integration, and complex queries.