Glazes is actually glass where you mix all kinds of powdered element from the periodic table and melt them at 1200C to hopefully get a result you like. A unusual kind of chemistry.
I am more interested in the glazes and the results he got than the crud app and the DB. Just read it in diagonal, but I don't see why a simple Django app wouldn't take care of this easily (with admin) and you use sqlite for local use case.
I'm about to assemble my Cerambot 3D printer and get into the game too :D
But yeah, the year is 2024, and the idea of using a relational database model to store relations is new again. Otherwise, this is a poster use case for SQLite.
I was taught that compression of clay is a big factor in ceramic strength.
I’m curious, how fragile are the pieces? Will a cerambot mug survive a small (eg 4”) drop?
Table 1: <piece id> <combo id> <location>
Table 2: <combo id> <glaze id> <priority>
Location specifies where the combo is applied to the part; priority specifies ordering of the glaze layers (glazes whose order doesn't matter have the same priority).
The only thinking that needs to be done is understanding that you don't mix glazes and combinations in a single project, but a project has a set of combinations associated with it, some of which may only have one glaze.
Writing the requisite SELECT queries (getting all pieces that use a glaze, or vice versa) is left as an exercise to the reader (which, I hope, is straightforward - but the same can be said of the schema).
This article does a lot of mental gymnastics to avoid using a relational database to store relations. NoSQL has its places (e.g. sometimes, a KV store is a KV store), but this isn't it.
Sometimes I feel like the NoSQL hype did some collective damage to the way people think about data. But then again, I'm not a database architect, so what do I know.
But I suppose this is an ad for the writer's graph database anyway.
What is it that you think they wanted, and why doesn't keeping the data locally make sense?
If what they wanted is learning a graph DB API, then sure. Otherwise, please elaborate.
To me, this looks like a perfect fit for a SQLite database (see my other comment). Their entire dataset has a smaller size than the HTML page you're reading right now.
If they wanted cloud sync, they could simply send the entire thing over the wire. Or, you know, use SQL.
Though unless they're running a custom-order ceramics factory, that'd be an overkill. But hey, they'd learn why SQL is useful from that.
> I also happen to know the founders of Instant, which bills itself as a graph-based Firebase
as "to be one of the founders"
Regardless.