Arangodb roles code#

Arangodb roles code#

While we provide a lot of compatibility code and try to keep the core modules compatible where possible, a big difference is that Node.js is generally used to perform asynchronous operations while in ArangoDB all operations are synchronous. The good thing is you can get started with the built-in job queue right away and still move on to a dedicated solution if the need arises during development.Īs for middleware and NPM packages: Foxx is not fully compatible with Node.js code. However depending on your requirements an external job or message queue may be a better fit.

Also when using computationally expensive cryptography this will affect the performance of the database (because unlike Node.js Foxx is strictly synchronous and thus all operations should be considered blocking).ĪrangoDB does not support role-based authentication out of the box but it is perfectly reasonable to implement it within ArangoDB using Foxx (just like you would implement it in Node.js, except you don't need to leave the database).įor sessions there are generally two possible approaches: you can either use a collection with session documents (using ArangoDB as your session backend) or you can keep your services stateless by using signed tokens (Foxx comes with JWT support out of the box).Ĭomplex/stored queries and input validation (using the joi schema library originally written for hapi) are actually some of the main use cases of Foxx so those shouldn't be any problem whatsoever.įoxx comes with its own mechanism for queueing tasks, which can also be scheduled ahead or recur periodically. HMAC signing and PBKDF2 key derivation for passwords) the support is not as exhaustive and extensible as in Node.js. While ArangoDB does support some cryptography (e.g. You can use ArangoDB Foxx as the sole backend of your application, however it is important to keep the limitations of Foxx (compared to a general purpose JS environment like Node.js) in mind when doing this. Side question (that might answer some of the above): Could Foxx utilise some of the node middleware available via npm? Entry parsing, validation and sanitization.Complex querying (root of my initial thought, as to avoid multiple hops between DB and back-end).Should and could one use arangodb + foxx to create the complete back-end stack for serving a REST API, thus avoiding another layer/component in the stack? e.g. The project will be developed with Javascript for the whole stack, using the NodeJS ecosystem.

The API would then be consumed by several web and mobile front-end frameworks to handle the rest of the logic. Considering the app needs for the back-end, I have concluded that most, if not all, of it could be served through a REST API as to aid cleaner design for future development and integration with others. I am working on an app that would greatly benefit from Arangos' multi-model capabilities.