{"id":51979,"date":"2016-08-25T00:00:00","date_gmt":"2016-08-25T07:00:00","guid":{"rendered":"https:\/\/griddb-linux-hte8hndjf8cka8ht.westus-01.azurewebsites.net\/blog\/what-is-griddb\/"},"modified":"2016-08-25T00:00:00","modified_gmt":"2016-08-25T07:00:00","slug":"what-is-griddb","status":"publish","type":"post","link":"https:\/\/griddb-linux-hte8hndjf8cka8ht.westus-01.azurewebsites.net\/en\/blog\/what-is-griddb\/","title":{"rendered":"What is GridDB\u00e2\u201e\u00a2"},"content":{"rendered":"

Toshiba GridDB\u00e2\u201e\u00a2 is a highly scalable NoSQL database best suited for IoT and Big Data<\/h2>\n
<\/div>\n

We live in the world of Internet of Things (IoT) where billions of devices are interconnected generating petabytes of data. Gaining insights and information from that data and generating value out of it give competitive advantage to businesses, organizations, governments, and even individuals.<\/p>\n

Companies should focus more on creating value from the data that would be useful to enhance their core products, services or even operational processes and not spend time in dealing with the complexity surrounding Big Data (data in large quantities, high frequencies, and vast varieties).<\/p>\n

GridDB is an innovative solution built within Toshiba to solve these complex problems faced by its numerous customers. The foundation of GridDB’s principles is based upon offering a versatile data store that is optimized for IoT, provides high scalability, tuned for high performance, and ensures high reliability.<\/p>\n

<\/div>\n

Four Pillars of GridDB<\/h2>\n
<\/div>\n
    \n
  1. Optimized for IoT<\/li>\n
  2. High Performance<\/li>\n
  3. High Scalability<\/li>\n
  4. High Reliability \/ Availability<\/li>\n<\/ol>\n
    <\/div>\n

    1. Optimized for IoT<\/span><\/h2>\n
    GridDB’s Key Container data model and Time Series functions are purpose built for IoT<\/div>\n
    \n

    Key Container data model of GridDB extends the typical NoSQL Key-Value store. Key Container model represents data in the form of collections that are referenced by keys. The key and the container are rough equivalents of the table name and table data in the Relational Database (RDB). Data modeling in GridDB is easier compared to other NoSQL databases as we can define the schema and design the data similar to that of an RDB.<\/p>\n

    Key Container model allows high speed access to data through Java and C APIs. Data in GridDB is also queried through TQL, a custom SQL-like query language. Basic search through WHERE command and high speed conditional search operations through indexing offer great advantage for applications that rely on faster search. GridDB supports transactions including those with plural records from the application. Transactions in GridDB guarantee ACID (Atomicity, Consistency, Isolation, and Durability) at the container level.<\/p>\n

    Two types of containers are prominent in GridDB: Collection-Container, a general-purpose container; and TimeSeries-Container for managing time series data.<\/p>\n

    \"image01_e\"
    \nTimeSeries-Container is apt for IoT scenarios where the data is associated with a time-stamp. GridDB supports numerous time series functions such as<\/p>\n