WIP
ndgom builds on ndgo and aims to give orm like experience for dgraph graph db
Coz it's fun.
Just look at the name alone. Let's break it down:
g- graphdg- dgraph, the graph databasego- The Go Programming Languagedgo- dgo - the Dgraph Go clientndgo- ndgo - iterates on dgo adding low-abstraction abstractionsm- as in map/mapper - adds mappingsom- object mappings?gom- graph object mapping (as opposed to orm). Why not ogm? Because it would be too similar in name to dgogm and would add 2 characters instead of one to the name, that would be inefficient!m- magic! Initially, I planned ndgo to have an ndgo.Magic{} helper, but decided to keep it simple there - all the magic will happen here.ndgom- all of the above.
Isn't it fun?
Everything may or may not change ¯\_(ツ)_/¯