\n
![\"\"](\"https:\/\/griddb.net\/wp-content\/uploads\/2018\/01\/containers_intro.gif\")
<\/p>\nGridDB offers two different editions (Community or Standard) each of which have an increased number of features relative to its predecessor. Both editions provide ACID compliance, high scalability, and high performance through an in-memory architecture. They also all provide high reliability and availability due to its hybrid cluster architecture. This blog intends to reveal the biggest differentiators between the different editions. This will naturally lead to some real-life \u00e2\u20ac\u201d although limited \u00e2\u20ac\u201d examples or scenarios in which one edition may be superior to another.
\nGridDB Community Edition (CE)<\/b> is the free and open-source version. This version can be considered as the most basic version of GridDB, though it still provides many benefits and features over other NoSQL databases. GridDB CE is available under the AGPLv3 license and was built with high performance, scalability, and fault tolerance in mind.
\nGridDB Standard Edition (SE)<\/b> is the commercial version of GridDB. GridDB SE provides extra software support with updates, patches and provides new tools and features not seen in Community Edition. These include online node additions, a web dashboard, a command-line shell for cluster management, and spatial data types.<\/p>\nCommon Features<\/h2>\n
Catered to IoT Data<\/h4>\n
GridDB is tailored for IoT data by using a key-container model of storing and accessing data. In many IoT applications, many devices report data very frequently and have timestamps associated with them. GridDB provides a TimeSeries<\/b> container that can handle timestamp data that arrive at high rates. TimeSeries containers provide aggregation and sampling functions along with data compression as a way to save storage space.
\n<\/p>\nHigh Performance<\/h4>\n
GridDB uses a Memory First, Storage Second<\/i> approach to accessing data. Frequently accessed data is stored in-memory and preferably within the same block. GridDB’s precise and effective use of multi-threading and CPU allocation reduce the overhead of database operations. Performance is further increased through parallel processing within and across nodes. This allows GridDB to make maximal use of memory and CPU. GridDB Community Edition<\/b> is the open-source version of GridDB. Version 3.0.1<\/b> is free and available for download on the GridDB Downloads page<\/a> along with its various connectors. GridDB Community Edition can be deployed in a public cloud environment and has an AMI<\/a> available through AWS. GridDB brings pivotal features like:<\/p>\n GridDB Community Edition is fully open-source and provides APIs and connectors to several frameworks for developers. GridDB has APIs in C, Java, Python, and Ruby. Developers can use the connectors to YCSB, Apache Spark, Hadoop MapReduce, Kafka, and KairosDB. When using Community Edition, a GridDB cluster can be composed of many nodes. The procedure for adding new nodes is fairly simple and straightforward: simply stop the cluster and rejoin all the nodes (including the new<\/i> node). Then, login as the Now that the cluster is stopped, the new node is ready to be added. Simply ensure that the new node has the same cluster definition file<\/b> ( Node entry can also be specified with from another node (as long as all nodes are started with Having seen how to add nodes in an already functioning cluster on Community Edition is important because it will provide some context for the next section.<\/p>\n GridDB Standard Edition is the commercial version of GridDB. GridDB Standard Edition gives software support with maintenance releases, bug fixes, patches, updates, and company support 24\/7, 365 days a year. GridDB also provides an AWS AMI<\/a>. GridDB SE brings in useful utilities like:<\/p>\n Spatial data are data points that can be mapped and stored as points or as topologies in a coordinate space. Spatial data is used heavily in Geographic Information System (GIS) applications and map information systems. Spatial data that captures aspects of location are also quite frequently in IoT applications. Examples of spatial data include geometries like POINT, LINESTRING, POLYGON<\/i>. Spatial data is represented with GridDB provides a command line interpreter to operate on GridDB. This tool is known as Expansion in a database involves increasing its size and capacity. This translates to adding more nodes so that it may scale out with commodity hardware. For most databases, adding more nodes can only be done when the database is offline. GridDB Standard Edition offers the ability for users to expand their database online without having to stop operation and halt services. When adding new nodes to a cluster in Community Edition<\/a>, all the nodes in the cluster must leave the cluster and be restarted. This can be tedious and costly for a large database with many nodes. In Standard Edition, this step can be skipped altogether. Standard Edition also features online backup so periodic backups can be executed on a cluster as a safeguard against data corruption or application malfunctions.<\/p>\n Standard Edition provides export and import tools so GridDB nodes can recover from local damages and containers can be migrated, even from an RDB database. The export<\/b> function of GridDB allows developers to export whole clusters, individual databases and containers, user rights, and row sets resulting from search queries. Exported data can be stored either in csv<\/i> or binary<\/i> formats. Individual or multiple containers can be exported into single files known as container data files<\/i> as well.
\n![\"\"](\"https:\/\/griddb.net\/newen\/wp-content\/uploads\/2018\/02\/hybrid_cluster_management.png\")
<\/a><\/p>\nGridDB Community Edition<\/h2>\n
Open Source and Well Documented<\/h4>\n
\nSource code for GridDB, its APIs, and its connectors can be viewed on GitHub<\/a><\/p>\nSetting Up and Adding Nodes in Community Edition<\/h4>\n
gsadm<\/code> user on all node machines. From there, have each node in the current cluster leave the cluster. Then stop the node.
\nOn each of the old nodes:<\/p>\n\n$ sudo su - gsadm\n$ gs_leavecluster -u username\/password\n$ gs_stopnode -u username\/password\n<\/pre>\n
gs_cluster.json<\/code>) as all the other nodes. From there, start all the nodes and join them into the cluster. Now the GridDB cluster is operating and ready for use with the new nodes.
\nIn this example, we will add a new node at IP address 192.168.0.1<\/code> to a cluster named cluster1<\/code> which is made up of 3 nodes<\/b>.
\nOn all the nodes (both old and new), issue:<\/p>\n\n$ gs_startnode\n$ gs_joincluster -c cluster1 -u username\/password -n 4 -w\n<\/pre>\n
gs_startnode<\/code> beforehand). In this case, the cluster will not begin operation until all 4 nodes have been joined (-n 4<\/code>).
\nWe will add the new node by issuing:<\/p>\n\n$ gs_joincluster -c cluster1 -n 4 -s 192.168.0.1:10040 -u username\/admin\n<\/pre>\n
Key Features of GridDB Standard Edition<\/h2>\n
Spatial Data Types<\/h4>\n
GEOMETRY<\/code> columns in GridDB. Developers can add spatial columns and spatial indexing to their containers. One can also make geometric queries using TQL such as spatial intersections. Developers can also create geometry objects and execute geometric functions using the C and Java APIs of GridDB Standard Edition.
\n
\nMore detailed information on Geometric data can be found on the using geometry values<\/a> post.<\/p>\nWeb Management GUI<\/h4>\n
\nGridDB Standard Edition provides an intuitive, easy-to-use management dashboard application that runs in Apache Tomcat. With the web application, users can see and manage their GridDB clusters and repositories. Users and administrators can also view and manage the configurations, connections, and settings of the nodes with the GridDB cluster, as well as issue and analyze TQL queries. Snapshots can be taken of nodes to view individual nodes and their performances at points in time. Individual containers can be listed and its properties and data can be managed from the dashboard as well. General system information like checkpoint and backup information can also be seen in the GUI application. Errors, logs, and events that have occurred on containers and GridDB clusters are available for listing and analysis through the management GUI are also included.
\n<\/p>\nCluster Management Shell<\/h4>\n
gs_sh<\/code> that can be accessed from the gsadm<\/code> user. This command line tool allows a user to manage cluster and data operations in GridDB; clusters can be easily defined and their status and logs can be displayed. Individual nodes can be started and stopped from a cluster in gs_sh<\/code> as well. GridDB containers and triggers can be listed and displayed. Indexes can be added and dropped from containers at will and TQL operations can be performed on containers through the shell.
\nThe gs_sh<\/code> can be used in two different modes. The first mode offered is interactive mode<\/b> where special GridDB-specific commands can be entered like a traditional command-line. The second mode offered is batch-mode<\/b> which involves the use of a script file in the .gsh<\/code> format that contain series of subcommands to execute on GridDB.<\/p>\nOnline Backup and Online Expansion<\/h4>\n
\nTo add new nodes in GridDB Standard, simply use the gs_appendcluster<\/code> command. Specify the cluster that you wish to add to as well as the IP address and port of the node machine. For example to add a node with IP address 192.168.0.3<\/code> to a cluster named largeCluster<\/code> you would issue:<\/p>\n\n$ sudo su - gsadm\n$ gs_appendcluster --cluster largeCluster 192.168.0.3:10040 -u username\/password\n<\/pre>\n
Differential Backup Function<\/h4>\n
<\/a>
\nGridDB Standard Edition adds a new backup type known as differential or incremental backup<\/i>. In incremental backup, the cluster database is stored in node units in a backup<\/i> directory. For future backups, only the differences between the update block and the last backup get backed up. Updated data blocks are only backed up once a specified baseline is executed. Differential backup can also be done online.<\/p>\nExport \/ Import Tools for Migration<\/h4>\n
\nThe import function<\/b> can be used to migrate a relational database into GridDB. Just like the export function, individual containers, databases, and clusters can be imported in GridDB. The way that the relational database translates to a GridDB database can be specified with a resource definition, an RDB collection function, a mapping function, and a GridDB registration function.
\n<\/a>
\nImports and export processes can be sped up by being executed in parallel. Details and instructions for using the export and import functionality can be found in this section<\/a> of the documentation.<\/p>\nSetting Up Nodes in Standard Edition<\/h5>\n