I agree on that point: having nice tools as Ecto for a large number of database engine would be great.
But it’s a lot of work, and hard work too and I think that for almost every language, the number of available tool depends on… the community. Because it is time and work and everybody has a limited amount of each.
Then sometimes, the best thing to do when you don’t find what you need is to build it yourself or at least try to build it yourself and to share it with the community. And if you’re lucky, some people will help you to build the thing.
Elixir is not so popular that there is a lot of mighty brilliant individuals achieving all the things just for the fun then we have to build things ourselves. There’s a lot of people in this forum who’ve contributed in one way or another to Elixir ecosystem (thank you guys :)). Why don’t you bring your love of alternative dbs and your love of Elixir into a new library and share it with us? It can (will?) be hard but you’ll learn a lot but after that Elixir will appeal more people like you :).
@marcalchca I’m the author of ecto_neo4j and I strongly discouraged you from using because I will stop maintaining it really soon. It’s very unsatisfying to work on it as developer (imagine putting squares in triangles…) and imo not satisfying as an end user as it rely on relational-concept.
Then, you maybe should use seraph which way more graph friendly and heavily inspired by Ecto (an rely on it for some parts). I didn’t make a annoucement yet because I want to add the query api first, I hope it will be available next week.
.
