diff --git a/roadmaps/mongodb/content/expiring@butGgZXGPTZI-sWx24bOr.md b/roadmaps/mongodb/content/expiring@butGgZXGPTZI-sWx24bOr.md index 7de13518c..4616871b5 100644 --- a/roadmaps/mongodb/content/expiring@butGgZXGPTZI-sWx24bOr.md +++ b/roadmaps/mongodb/content/expiring@butGgZXGPTZI-sWx24bOr.md @@ -1,6 +1,6 @@ -# Expiring +# Expiring Data with TTL Indexes -Expiring indexes (TTL - Time To Live) in MongoDB automatically delete documents from a collection after a specified period, making them ideal for managing time-sensitive data like session information, log entries, temporary caches, or any data that becomes obsolete after a certain duration. These indexes are created on date fields and use a background process that runs every 60 seconds to remove expired documents, helping maintain optimal collection size and performance by preventing the accumulation of outdated data. TTL indexes are particularly useful for applications that generate large volumes of transient data, as they provide an automated cleanup mechanism that reduces storage costs and improves query performance without requiring manual intervention or complex application logic to handle data expiration. +TTL (Time-To-Live) indexes are a special type of index that automatically remove documents from a collection after a certain amount of time has passed or at a specific clock time. By defining a TTL index on a field containing date values, the database background process continuously monitors the collection and deletes documents once the specified duration has elapsed. This feature is commonly used for managing temporary data like session logs, cached items, or temporary verification tokens that are no longer needed after a set period. Visit the following resources to learn more: diff --git a/roadmaps/mongodb/content/queryable-encryption@LpfuM6SuhlNNjBcHM68ee.md b/roadmaps/mongodb/content/queryable-encryption@LpfuM6SuhlNNjBcHM68ee.md index 97d7d84db..d1ef7764c 100644 --- a/roadmaps/mongodb/content/queryable-encryption@LpfuM6SuhlNNjBcHM68ee.md +++ b/roadmaps/mongodb/content/queryable-encryption@LpfuM6SuhlNNjBcHM68ee.md @@ -1,6 +1,6 @@ # Queryable Encryption -Queryable Encryption is MongoDB's advanced security feature that allows you to encrypt sensitive data while still being able to query it efficiently without decrypting the entire dataset. This cryptographic technique enables applications to perform equality queries on encrypted fields using deterministic encryption and range queries using order-preserving encryption, providing a balance between data security and functionality. It's particularly valuable for applications that need to comply with strict data protection regulations while maintaining the ability to search and filter encrypted data, such as healthcare systems handling patient records or financial applications managing sensitive transaction data. +Queryable Encryption is a feature that allows you to perform expressive queries on data while it remains encrypted on the database server. It ensures that sensitive information is stored in an encrypted state at all times, even while in use by the application, by using client-side encryption keys that are never shared with the database. This allows users to search, filter, and retrieve specific records without needing to decrypt the entire dataset on the server, balancing data privacy with functional database performance. Visit the following resources to learn more: diff --git a/roadmaps/mongodb/content/tls--ssl-encryption@5F7zAAnvnVTTnBzOB7TSu.md b/roadmaps/mongodb/content/tls--ssl-encryption@5F7zAAnvnVTTnBzOB7TSu.md index 917cc4622..b7438a166 100644 --- a/roadmaps/mongodb/content/tls--ssl-encryption@5F7zAAnvnVTTnBzOB7TSu.md +++ b/roadmaps/mongodb/content/tls--ssl-encryption@5F7zAAnvnVTTnBzOB7TSu.md @@ -1,6 +1,6 @@ # TLS / SSL Encryption -TLS/SSL encryption in MongoDB provides secure communication channels between clients and the database server, as well as between replica set members and sharded cluster components, ensuring that data transmitted over networks is protected from eavesdropping and tampering. This transport layer security encrypts all network traffic using industry-standard cryptographic protocols, supports certificate-based authentication for enhanced security, and can be configured for mutual authentication where both client and server verify each other's identities. Implementing TLS/SSL is essential for production deployments, especially in cloud environments or when MongoDB instances communicate across untrusted networks, as it prevents man-in-the-middle attacks and ensures data confidentiality during transmission. +TLS (Transport Layer Security) and its predecessor, SSL (Secure Sockets Layer), are cryptographic protocols that establish an encrypted link between a client and a server. By using these protocols, data transmitted over a network is protected from eavesdropping, tampering, and forgery. When configured for a database, this ensures that all information exchanged between the application and the server remains private and secure throughout the entire connection process. Visit the following resources to learn more: