Re:ArangoML Pipeline: Common Metadata Layer for Machine Lear...
by joerg84 on Wednesday September 25, 2019 @12:41PM
(#21072462)
Did you try the Kubernetes Operator: https://github.com/arangodb/kube-arangodb? Should at least help with the k8s part... Also would be curious about your sharding challenges, feel free to ping me on the ArangoDB slack
Re:ArangoML Pipeline: Common Metadata Layer for Machine Lear...
by noah-kun on Wednesday September 25, 2019 @12:59PM
(#21072683)
Yes, I struggled with the operator, to the point where it would not install at all. I even fixed some of the documentation, but later my database was not responsive.
I ended up using the somewhat deprecated community-made .yaml files in https://github.com/sbaugher/arangodb-kubernetes
It has a problem of it's own, but I have some idea how to fix it (next time it happens), and am very interested in Oasis.
I admit I liked Mongo for it's document storage. But I didn't like Postgres due to my irrational dislike of SQL Then I challenged myself to try out a graph database.
ArangoDB presents things like Mongo (as documents), has a much nicer query language than SQL (or just use GaphQL) and does graph stuff; all while being amongst the top 3 or so in benchmarks that are designed to test only specific types of databases. If databases did triathlons, ArangoDB would be unbeatable.
Only two issues that I struggled with are/were Kubernetes cluster stuff, like sharding, but this is common to cluster DBs I think.