> You don't need a set, map, heap, stack, array, hash etc database. On the contrary, redis is super popular, and that is basically what it is. > More concrete

> You don't need a set, map, heap, stack, array, hash etc database. On the contrary, redis is super popular, and that is basically what it is. > More concretely I'm pretty sure you could demonstrate using relational algebra that any graph can be formed pretty trivially using relations. So I think there is probably provably no use case that can't be done with a more traditional RDBMS. The question would be more about efficiency & ease of use than if you could literally just store a graph in a rdbms