A Cose Look at Taban: the JSON REST Database for OSGi

The concept behind Taban is that the web Application will use HTTP protocol like GET, PUT, DELETE methods to perform CRUD (Create , Read , Update and Delete) operation by using JSON as a Data Exchange Format. By default, the data in JSON gets stored in a db4o object database.  Conversely, it can convert JSON into real object and saves them to db4o database. Taban is supposed to be implemented as a component of OSGi bundles.

Taban handles URL in the following way in REST environment.

• GET: If there is a forward slash at the end of the URL, it will return elements of a JSON array. In case of no forward slash at the end, it will return JSON content at the location directly.
• PUT: If the URI ends in a forward slash the JSON content will be inserted and an ID will be generated automatically. The id is generated as an auto-increment of the integer for the particular URL. If the URI does not end in a forward slash the JSON content will overwrite previous content at that address,  otherwise, it will insert at the location.
• Delete: This method supports URL without any forward slash.

There is going to be different additional HTTP Headers other than the above HTTP methods. Those headers will control the HTTP response either by filtering or limiting the results. If you use rich client to load most of your functionality then the web application can use Taban for data persistence without much effort to set up back end server application. It also allows you to set up complex server services if your application demands it. Taban is compatible with any front end technology as long as it supports HTTP services.