请输入您要查询的百科知识:

 

词条 Draft:GridDB
释义

  1. History

  2. Main Features

      In-Memory Architecture    Key-Container Model    Hybrid Master/Slave Architecture    ACID-Compliant    Replication    Failover[14]  

  3. References

{{AFC submission|d|adv|u=IllegalThoughts|ns=118|decliner=Mjs1991|declinets=20190307021851|ts=20190213201939}} {{infobox software
| name = GridDB
| developer = Toshiba
| license = Proprietary (enterprise), AGPL (community)
| genre = Key-value database, NoSQL database
| programming language = C++
| language = C/C++, Java, Python, Go, PHP, Perl, and Ruby
| latest release version = 4.1.[1]
| website = {{URL|www.griddb.net/}}
| repo = https://github.com/griddb/griddb_nosql
}}

GridDB is a scalable database for IoT[2] (Internet of Things) and Big Data applications[3]. Both community and enterprise editions are available[4], where the former is licensed under the GNU Affero General Public License (AGPL). It is written in C++[5] and has language bindings for C/C++, Java, Python, Go, PHP, Node.js, Perl, and Ruby.

History

Toshiba began developing GridDB in 2011 with its first commercial

release coming in 2013 -- it was then open-sourced in 2016[6]

Main Features

In-Memory Architecture

Most of GridDB's storage occurs in-memory[7].

Its internal memory structure is flushed to disk on a checkpoint

interval while maintaining a transaction log between checkpoints. When

the database outgrows the configured memory utilization, data not likely

to be used soon is freed from memory.

Even when the database does not fit in-memory, GridDB's performance

remains stable without the user having to perform maintenance.

Because of this, GridDB rates highly on benchmark tests.[8]

Key-Container Model

GridDB uses a modified version of the popular key-value data model [9]. The key can be

either any user-specified value or a timestamp. Each container can

be specified via a key and then be further queried like a traditional

relational database management system (RDBMS); the data inside the

container is very similar to a RDBMS as well.

GridDB uses both Collections and TimeSeries containers.

Containers of the Collections type can use any value as a key, while

TimeSeries Containers need to use a time value. This allows for a

specialized handling within the application, along with other features

(ex. TIME_AVG, TIME_NEXT, TIME_SAMPLING). Explicit time functionality

allow for special time functions for data which require it.

Hybrid Master/Slave Architecture

GridDB has a hybrid master/slave

architecture [10].

The nodes in a cluster are organized in such a way that one of the nodes

is elected master, but every single node has the partitioning data

needed to organize the cluster. If the master fails, a bully election is held to quickly promote another node back

up to the master position. This eliminates the single point of failure found in traditional master/slave architectures while

maintaining the high performance that they possess.

ACID-Compliant

GridDB is ACID-compliant on the container level.[11]

GridDB allows the user to configure the database to allow immediate

consistency or eventual consistency.[12]

Replication

The degree/levels of Replication can be set

by the user for the entire cluster.[13]

Each partition has many nodes: the owner, enough backup nodes to comply

with the user-configured replication level, and any catch up nodes for

the specified replication level.

Catch up nodes are used when there's an issue with enough of the

individual backup nodes to mean that the replication level is not being

satisfied. Reads and writes are direct to the partition owner rather

than requiring a quorum of peer-to-peer nodes.

Failover[14]

Monitoring of the nodes in the cluster is the job fulfilled by the

master node. If a node does not respond to the master's heartbeat, that node is marked as down/failed. The master

then assigns the partitions that node owns to the other replicas.

If replication level is not met after a failure, another node will be

assigned the role of catch up node. Which will trigger an event which

will cause the partition to begin transferring large blocks of data and

making sure all data is safe.

References

1. ^{{cite web |title=Toshiba' s Scale-out Database GridDB Now Reinforced with Enterprise-Grade Long-Term Archiving of IoT data |url=https://www.toshiba-sol.co.jp/en/news/detail/20190115.htm |website=Toshiba Corporate Website |accessdate=23 January 2019}}
2. ^{{cite web |title=DENSO & Toshiba |url=https://special.nikkeibp.co.jp/atclh/tomorrowtech/toshiba_denso/ |website=Nikkei Business Publications |accessdate=23 January 2019}}
3. ^{{cite web |title=System Poperties |url=https://db-engines.com/en/system/GridDB |website=db-engines |accessdate=23 January 2019}}
4. ^{{cite web |title=Toshiba’s Innovative GridDB NoSQL Database Affords Unlimited IoT Possibilities |url=https://www.businesswire.com/news/home/20170424005047/en/Toshiba%E2%80%99s-Innovative-GridDB-NoSQL-Database-Affords-Unlimited |website=Business Wire |accessdate=23 January 2019}}
5. ^{{cite web |title=GridDB GitHub |url=https://github.com/griddb/griddb_nosql |accessdate=28 November 2018}}
6. ^{{cite web |title=Toshiba Releases High Scale Database "GridDB" as Open Source To collaborate with big data technologies and create new value |url=https://www.toshiba-sol.co.jp/en/news/news201602_01.htm |website=Toshiba Digital Solutions Corporation News |accessdate=23 January 2019}}
7. ^{{cite web |title=GridDB Solutions Toshiba | url=http://www.solutions.toshiba.com/griddb.html | website=www.solutions.toshiba.com |accessdate=9 January 2019}}
8. ^{{cite web |title=GridDB and Cassandra YCSB Benchmarks |url=https://griddb.net/en/blog/griddb-and-cassandra-ycsb-benchmarks/}}
9. ^{{cite web |title=Digital T-Soul – High Speed and scalable processing of ever-growing time-series data |url=https://www.toshiba-sol.co.jp |website=TDSL digital magazine |accessdate=23 January 2019}}
10. ^{{Cite web|url=http://www.griddb.org/griddb_nosql/manual/GridDBTechnicalDesignDocument.pdf|title=GridDB Technical Design Document|last=|first=|date=|website=|archive-url=|archive-date=|dead-url=|access-date=2018-11-28}}
11. ^{{cite web |title=GridDB complies with ACID |url=https://griddb.net/en/blog/griddb-complies-acid/ |website=GridDB Blog |accessdate=23 January 2019}}
12. ^{{cite web |title=Purpose built-in memory NoSQL database for IoT |url=https://www.youtube.com/watch?v=P2a2VYaiyYA |website=YouTube |accessdate=23 January 2019}}
13. ^{{Cite web|url=https://griddb.net/en/docs/manuals/v3.1/GridDB_TechnicalReference.html#sec-4.4.8|title=GridDB technical reference|website=GridDB|language=en|access-date=2017-12-01}}
14. ^{{cite web |title=Whitepaper: GridDB Reliability and Robustness |url=https://griddb.net/en/docs/GridDB_Reliability_and_Robustness_1.0.7.pdf |website=GridDB Whitepaper |accessdate=23 January 2019}}
随便看

 

开放百科全书收录14589846条英语、德语、日语等多语种百科知识,基本涵盖了大多数领域的百科知识,是一部内容自由、开放的电子版国际百科全书。

 

Copyright © 2023 OENC.NET All Rights Reserved
京ICP备2021023879号 更新时间:2024/11/12 14:37:59