Test Driven Development I have been one of the lucky attendants of scotland.js in Edinburgh recently. It was a really nice & informative conference, thanks to all people that made it possible. I did really like to see that TDD is reaching the front-end developers finally. A lot of useful tools for this have been presented by James Shore, Bernard Kobos and Sebastian Golasch. In ArangoDB, TDD is in action all day and I am looking forward to improving our front-end testing even further using these awesome tools. Front-end Development meets NoSQL Furthermore several talks focussing on front-end development have been given, e.g. by Gregor Martynus presenting Hoodie.js. These front-end talks and my discussions with other attendees gave me the impression that front-end developers spend a lot of time deciding which database they should use.
It has taken some time, but now part 2 of the Foxx Screencast is available. I talk about some more advanced topics of Foxx and also plans for the future.
Starting today you can install the first Alpha of the upcoming release of ArangoDB version 1.3. Some of the new features are: ArangoDB Foxx: A lightweight way to define APIs directly on top of ArangoDB Traversals: Define traversals to explore your graphs stored in ArangoDB A new and improved Frontend: Featuring a new design and various improvements And more: Multi-Collection transaction support, user defined functions in AQL, more builtin AQL functions and AQL improvements, bug-fixes… ArangoDB Foxx: The first screencast If you want to get a first look at ArangoDB Foxx, you can now see our first screencast. Lucas talks about the motivation and goals of Foxx and introduces you to the basics. A second screencast will follow with more advanced techniques like our Repositories and Models: How to install it? If you are on a Mac and using Homebrew, you can install it now via brew install –devel arangodb. If you are compiling ArangoDB by yourself, checkout the branch 1.3 from github and compile it. if you are using Linux, we have create package for the usual distributions. You can download them from here.
ArangoDB follows the Common.JS specification for modules. However, it would be very convenient, if there was an easy way to install a package like “underscore.js”. These package are, for instance, available using NPM. There is a draft for packages on Common.JS which seems to be compatible with NPM. NPM has a neat way of dealing with version conflicts. Basically, it allows multiple versions to exists simultaneously. For example, assume you have 4 packages A, B, C, D. A requires B and C and D, B requires C. Then directory layout might be as follows. node_modules | +- A | | | +- node_modules | | | +- B | | | | | +- node_modules | | | | | +- C (1.0.0) | | | +- C (2.0.0) | +- D Package B will see package C in version 1.0.0, while package A sees package C in version 2.0.0.
arangosh, The ArangoDB shell, provides some options that may simplify an ArangoDB user’s life. Some of these options have been added in version 1.1.2, and some options have been around for a while but are probably still less known. It’s time to showcase them.