Speaking for my own experience, I view Foxx services as not just unavoidable, but absolutely necessary, and one of the biggest defining factors of ArangoDB.
There are very few (maybe one or two) DB platforms that integrate both logic and data code together. This allows you to do things with the data that simple are not possible using only one or the other. For instance, SQL code is great at dealing with rows and aggregations, but falls quite short when you need logic to create structures, handle complex transactions, or make external calls. At first, I thought Foxx was unnecessary, but over time, I have started moving more and more of my application into this layer. I have become a HUGE fan of ArangoDB, and believe Foxx is one of the best additions to a DB I’ve ever seen. — Kerry -- You received this message because you are subscribed to the Google Groups "ArangoDB" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/arangodb/9b829ae8-6ab7-4292-bcbe-0775bfbd4c91%40googlegroups.com.
