MongoDB to HCL OneDB term mapping
The commonly used MongoDB terminology and concepts are mapped to the equivalent HCL OneDB™ terminology and concepts.
The following table provides a summary of commonly used MongoDB terms
and their HCL
OneDB conceptual
equivalents.
MongoDB concept | HCL OneDB concept | Description |
---|---|---|
collection | table | In HCL OneDB, a collection (also referred to as a JSON collection) is just a special type of table. A JSON collection is similar to a relational database table, except it does not enforce a schema. |
document | record / row | In HCL OneDB, a document is sometimes referred to as a JSON document and is stored as a record or row in a JSON collection (table). |
field | column | While JSON documents allow for the storage of unstructured data with a flexible schema, you can also think of fields within the JSON document as similar to relational columns in that they define the attributes contained within the record. |
primary / secondary | primary server / secondary server | The MongoDB primary and secondary is equivalent to the HCL OneDB primary server and secondary server. However HCL OneDB secondary servers have additional capabilities. For example, data on a secondary server can be updated and propagated to primary servers. |
replica set | high-availability cluster | The MongoDB replica set is equivalent to the HCL OneDB high-availability clusetr. However, when the replica set is updated, it is then sent to all servers, not only to the primary server. |
sharded cluster | shard cluster | In HCL OneDB, a shard cluster is a group of servers (sometimes called shard servers) that contain sharded data. |
shard key | shard key | These concepts are equiavlent between MongoDB and HCL OneDB. |