Home

Überdust

Überdust is a data storage and brokerage web service for connecting data providers with data consumers and application developers. It's main focus is to provide storage, sharing & discovery of real-time data from objects, devices & building installations around the world via the Web.

How Überdust works

Überdust is a web service designed to facilitate data sharing via the Web. Publishing and subscribing to the service is platform agnostic since users can provide and consume data via REST and WebSocket calls. Users interested in retrieving data from the web service can obtain them in various formats such as Tab delimited text, HTML, JSON, RDF and more.

![uberdust](http://img85.imageshack.us/img85/4986/uberdust.png) Überdust is currently under development and is coded in Java™ using bleeding edge technologies such as [Spring Framework MVC](http://www.springsource.org/), [Hibernate](http://www.hibernate.org/), [JSP](http://www.oracle.com/technetwork/java/javaee/jsp/index.html) & [JSTL](http://www.oracle.com/technetwork/java/jstl-137486.html), [Resin](http://www.caucho.com/resin/) and more.

Überdust stores data to an RDBMS using the WiseDB component of the WiseML library based on the state of the art O/RM framework, Hibernate. Although Überdust was originally developed for storing sensor data from wireless sensor networks, any source can provide data as long as it is in a simple timestamp-based format and a small set of metadata is already provided in the persistence store. For more details on the persistence structure see the WiseML wiki page.

In order to achieve an efficient conversational communication between the user and Überdust we decided to use the Caucho Resin's WebSocket servlet implementation. So users (both providers and consumers) can use their preferred web socket library and start feeding the service with data. On the other hand, the Überdust installation must be contained within Resin Application server since our code so far supports only the Resin's Web Socket implementation. This restriction exists due to the fact that the Web Socket Standard is still in Draft state so there is no standard implementation for application servers.

See some examples using the Überdust.