Postgres is definitely a great choice if you want a taste of NoSQL-like flexibility while staying in the familiar SQL world. In my eyes, ArangoDB provides simil

Postgres is definitely a great choice if you want a taste of NoSQL-like flexibility while staying in the familiar SQL world. In my eyes, ArangoDB provides similar benefits if you want to move beyond SQL without going "all in" with a pure graph database. You can model your data as documents and use arbitrary joins to start with and then restructure your data in terms of edges and vectors when you run into situations where you would benefit from graph queries. It's not either-or and because ArangoDB is multi-model you can mix both approaches in the same queries.