![]() So we could use it, but what are the compelling reasons? I believe that ArangoDB can be a complete backend solution for delivering data to the frontend, using custom endpoints implemented in javascript for any logic too fancy for the standard API functions. It also seems to be a product of some very fine German engineering (it is an opensource project, but backed by a German database company) ArangoDB is only 5 years old, it has grown up in the modern era of computing, and it shows. There are a lot of things that traditional databases do wrong now… to be fair, MySQL is over 20 years old now, it comes from a completely different era of computing. Import/Export is as JSON files, cleanly separated into structure and data.A “pure” Graph DB can be rendered impractical by adhering to an ideology of graphy purity, a multi-model database does not suffer from ideology, by also acting as a document store and key:value store it can enjoy extremely high performance for operations which a graph model is ill-suited for. Like SQL, AQL fulfills this promise while being more readable. A good language provides expressive power, that is relatively few words are required to express your will and make the software carry it out. The flow of AQL is decidedly straightforward and it is far more readable than SQL. The Arango Query Language (AQL) resembles python and javascript by using for.Now I recognize it’s bloody brilliant, in fact it’s practically common sense. At first it seemed like a weird bolted on feature. Instead of proliferation of services you get consolidation. The microservices are js plugins that run inside it - snug up against the data where there is no communication overhead. But with ArangoDB instead of running a bunch of different services, you run just one: ArangoDB. Microservices are a big buzzword but they can also be a nightmare to manage. ![]() ![]()
0 Comments
Leave a Reply. |