Tutorial MongoDB - ¿Qué son los Documentos y Colecciones en una Base de Datos MongoDB?

Understanding MongoDB Documents and Collections

Introduction to MongoDB Documents

• The discussion begins with an overview of MongoDB documents, emphasizing the importance of understanding their structure before delving into databases.

• Unlike SQL databases, MongoDB stores data in JSON-like formats under a dynamic schema known as BSON.

Characteristics of MongoDB Documents

• A document is the fundamental unit of information organization in MongoDB, analogous to a row in relational databases.

• Each document consists of multiple key-value pairs, where keys are strings and values can vary in type.

• Key characteristics include:

• Keys cannot contain null characters or special symbols like '.' and '$'.

• Case sensitivity applies; thus, keys must be unique within a document.

Data Types and Structure

• Examples illustrate that documents can have different structures even if they share similar fields (e.g., age).

• No duplicate keys are allowed within a single document; each key must be unique.

• The order of key-value pairs matters; for instance, x: 3, y: 5 is not equivalent to y: 5, x: 3.

Document Examples and Nested Structures

• An example shows how documents can include nested structures such as arrays or sub-documents (e.g., name and surname).

• Unique identifiers are automatically generated for each document using functions like ObjectId.

Understanding Collections in MongoDB

• Collections serve as groupings for documents, akin to tables in relational databases but with more flexible structures.

• A collection can contain documents with varying schemas; however, it’s advisable to maintain some level of consistency among them.

Advantages of Structured Collections

• Grouping similar documents enhances retrieval speed due to locality—knowing the general structure allows for efficient access patterns.

Understanding Database Structures and Naming Conventions

Importance of Indexes in Databases

• Indexes facilitate quicker data retrieval within document structures, especially when documents are organized under a single collection.

• Having documents of a single type within the same collection enhances efficiency.

Naming Conventions for Collections

• Collection names must not be empty or contain null characters, as these are reserved for identifying the end of a collection.

• Avoid using reserved words like "system" in collection names to prevent conflicts with internal collections.

• Special characters such as dollar signs ($) and periods (.) should not be included in collection names due to their unique properties.

Structure and Relationships in Databases

• A database is defined as a collection of objects, similar to relational databases that utilize tables, indexes, and stored procedures.

• Collections consist of groups of documents; thus, a database can be seen as an aggregation of multiple collections.

Instance Management and Permissions

• Each instance can manage several databases, which may contain zero or more collections. It is possible to have an empty database without any collections.

• Every database has its own permissions and is stored separately on disk files. This ensures independence among databases even if they reside on the same server.

Best Practices for Database Names

• Database names should avoid null values and certain characters (e.g., quotes, greater than/less than symbols).

• It's recommended to use lowercase letters for naming databases due to case sensitivity issues; names are limited to 54 bytes.

Examples of Database Usage

• An example includes a user management database that handles all user-related information while another might store temporary data specific to the server instance.

Conclusion and Further Resources