Skip to content
This repository has been archived by the owner on Dec 9, 2021. It is now read-only.

CloudBase

tsutomi edited this page Nov 11, 2012 · 1 revision

CloudB is a storage system which has its point of force in the data distribution system, allowing data to grow dynamically, without any effort for the administrators/developers. One other point which makes it strong it's its model agnostic approach to data modeling: in fact, CloudB is not bound to any specific model (eg. SQL, XML, Key/Value, etc.), but instead it provides all the instruments to build autonomous data models which will sit on top of the distribution system. (see Paths for further information).

CloudBase is the most basic, fast, immediate data model (path type), which allows the access to data in a string key/value model, organized in user-defined grids.

Supported Features

Like any IPath implementation, also CloudBase supports transactional data processing, encapsulating operations in a secure, sequential access to the data storage.

Tabular Data

The data model managed by CloudBase handles data using grids designed by user a run-time. A single path instance can define up to 2^23 tables. Each table can define up to 2^23 columns.

The only data type allowed by a column is String, which is implied when defining the column.

Columns can specify indexes, which are used to optimize access to the data stored. When creating an index, it is possible to specify a locale (in the form "en-EN"), to sort values according to the culture specific locale. Indexes are crucial in the strategy of accessing data in an ordered manner: in fact, CloudBase doesn't support any built-in identity (eg. auto-incremental numbers, GUIDs, etc.), but instead it relies on the user-defined algorithms for uniquely identifying a single row of a table. An index is optimized to be sequentially accessed by the user to return also non-indexed data, to update a row or to delete it.

Files

Clone this wiki locally