The new release of the Appjangle platform contains a reworked and improved onedb synchronization engine. Details are available on the appjangle blog.

Both the onedb server and the onedb client libraries got a bit of a makeover; with the most important aspect being the increase of performance of RPC calls both within components of cloud engine and between cloud engine and clients. 

Access to these new features is provided through a new version of the Appjangle client libraries (0.0.14), which can be found on the Appjangle downloads page

The new version of client libraries (0.0.11) now supports the specification of arbitrary strings as types for realms. Although this has been possible in the public onedb API before, the RPC back-end could only request a limited number of realms, which has been fixed now.

In addition, the seed() operation has also been extended with an optional parameter specifying a seedType. This allows to potentially create seeds on different servers/cloud nodes.

The new maven dependencies is:

Alternatively, the standalone JAR can be obtained from the onedb website.

New client libraries for the onedb engine have been released as part of the appjangle platform:

See on the appjangle blog: Java Client Library Version 0.0.10 Released

Although the documentation for onedb is yet to be completed completely, having a look at applications built with the onedb engine can give a first impression on the capabilities of the platform as well as how applications can be built in a onedb ‘style’.

The first application is textsync (@textsync). textsync is a Java Swing application, which allows to monitor a collection of text files on the local hard disk, and synchronize these text files, or part of the text files to the appjangle cloud. The latest developments in the textsync app are reported in the textsync blog.


The second application is nodejump (@nodejumpapp). nodejump is a HTML5 web application, which aims to enable the composition of interconnected web pages at a rapid pace. The latest developments of the nodejump application are reported on the nodejump blog. A live version of the current editor is deployed at  


The most recent extension to the appjangle API, the appendDeep operation, illustrates a key principle in the onedb engine:

Instead of having table-style data (few columns with many rows), data, in order to scale, is broken down into a three. 

The onedb engine delivers best performance, mostly as results of its web-oriented nature, when pages have between 0 and 1000 children. The appendDeep operation in the appjangle API illustrates, how within this range of nodes, scenarios can be managed, in which the number of ‘children’ of a node exceed 1000.

The onedb web page has for the past few month offered a simple way to obtain an API key. This API key allowed to create an almost unlimited number of ‘micro-databases’ on a free onedb server (called realms).

In order to make the management of these databases easier, and in preparation of releasing the JavaScript API for the onedb database engine, it is no longer possible to obtain an API key from the onedb webpage.

Instead, API keys can now be obtained from the platform:

These API keys offer the same capabilities as the API keys offered on

The appjangle platform offers a few enhanced features for the Java API. In particular:

  • The operations ‘register’ and ‘login’ allow a traditional login model with username and password. For each application, a realm is created, for which the access secret can be obtained through the login operation.
  • The applications view and edit deployed on the appjangle platform enable
  • The settings application allows to keep track of your API key and also access a private data realm particular to your user.