[ajkjk]

I would definitely use a simple relational model for this. Or probably in practice just download the whole dataset and do everything locally because it's going to be so small.

But I suppose this is an ad for the writer's graph database anyway.

[IanCal]

It doesn't seem to be their database, and "download the dataset and do this locally" doesn't make sense to me in terms of building what they wanted.

[romwell]

>doesn't make sense to me in terms of building what they wanted

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.

[ajkjk]

oh, I misread

> 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.