Author Archives: Michael Hackstein
ArangoDB’s Foxx allows you to easily build an API to access your data sources. But now this API is either public or restricted to users having an account, but those still get unlimited access.
In many use cases you do not want to expose your data in this fashion, but you want to expose it with a more controllable access pattern and want to restrict the requests one user could issue in a certain time period. Popular examples for these API restrictions are Twitter or Facebook. This allows you to offer all of your data but only in limited chunks, and then possibly charge your customers to increase the chunk limit they can request.
All this is done via API keys, which are bound to a user and has become a common pattern to monetize the data you have collected. (more…)
We are working hard to improve usability and simplify the usage of Foxx which will be shipped with version 2.5. of ArangoDB.
We have learned from the past and collected a lot of feedback, thanks to all people using Foxx already. It helped us to identify the following three important areas of Foxx that should be improved:
- Debugging of Foxx apps
- Getting started with Foxx
- Development Mode
I recently had the chance to visit FullStack London, a well organized conference. Thanks a lot to Skills Matter. FullStack was opened by Douglas Crockford about “The Better Parts” of ES6. I cannot wait to start using them. Douglas was followed by Isaac Schlueter talking about open source in companies. Although this talk was not technical I learned a lot and it was very inspiring.
With the 2.2 release we proudly announce that we now offer the feature of multi collection graphs.
This allows you to group an arbitrary set of ArangoDB collections into one graph.
In order to do this grouping you execute the following steps in arangosh or Foxx:
- Require the general-graph module and create a graph.
12var graph_module = require("org/arangodb/general-graph");var graph = graph._create("myGraph");
- Add collections to be used as vertex collections. If the collections are not yet created, ArangoDB will create them for you.
- Create edge definitions between your vertex collections. These definitions create edge collections and allow you to store edges where source and target vertices come from the collections written in the definition. If you give vertex collections unknown to the graph they will be added to the graph.
FOSDEM is an absolutely open and free conference in Brussels, Belgium. The conference offers an impressive amount of developer rooms discussing a broad range of technical topics, including NoSQL and graphs.
After a funny and productive ArangoDB hackathon weekend Frank and I arrived at FOSDEM on Sunday noon. We were looking forward to the talks in the graph devroom, but unfortunately for us it was not possible to enter the room (it was overfull, indicating a great quality of talks).
At the next speakers change Frank and I managed to slip into the room and could enjoy two inspiring talks by Neo4J.
Afterwards it was my turn to present the graph visualization interface in ArangoDB in a still crowded room (slides).
After my presentation, we handed out all our ArangoDB t-shirts to our fans.
All together it was a great experience and a really huge amount of people visiting the same conference which impressed me a lot.
Thanks for the team at the Graph Processing devroom for giving me the opportunity to speak and for organizing such a great devroom.
We will meet again next year.
With ArangoDB we ship a nice and useful web interface for administration.
However we have not yet told you in a video what you can do with this interface.
This screencast will give a comprehensive overview over the features offered in the interface.
Using ArangoDB as your graph database?
you now have the opportunity to visualize your data graphically, using the “Graphs” tab in the admin interface.
In this post i will explain you how to do this:
Step 1) Configure the Interface
At first you have to configure the interface to display exactly the data you desire.
For the dataset you have two options:
- Select one vertex and one edge collection directly
- Select the graph by name created using the graphs api
- Manage your graphs
Then the interface offers you several advanced options:
- Decide if the graph is directed (only outbound edges are followed) or undirected (all edges are followed). By default we treat your graphs as undirected
- Define if you want to start at a random vertex in the graph. By default we will do that.
- Then you can define which of your attributes should be used as the label on the verticies. By default we will use the _key for this.
- Now lets bring in some colour. You can either use the same attribute for colouring as for labeling, but you can also use a different one
- Finally you can define a grouping of new nodes. This is useful to speed up the performance of the interface and to increase the usability. You can define a priority list of attributes here, which is elaborated from top to bottom: All vertices having the first attribute defined are grouped by its value. All other nodes are grouped by the second attribute if present etc.
In the latest version of ArangoDB (1.4) we have introduced a new tab in the Admin Interface: Graphs.
You can use this tab to view and modify your graphs stored in ArangoDB.
In this screencast you will get a short introduction on how to use the new system.
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. (more…)