The new version of MongoDB 5.0 has already been released and in this new version some quite interesting news are presented of which we can highlight the data collections in the form of time series, as well as support for API version control, support for the Live Resharding mechanism, among others.
For those who are unfamiliar with MongoDB, you should know that This DB supports storing documents in a JSON-like format, has a fairly flexible language for generating queries, can create indexes for various stored attributes, effectively provides storage of large binary objects, supports registry operations to change and add data to the database, can work according to the paradigm Map / Reduce, supports replication and building fault tolerant configurations.
Main new features of MongoDB 5.0
In this new version we can find that problem numbering scheme has been changed and has been transitioned to a predictable versioning schedule. Once a year, a significant version will be formed (5.0, 6.0, 7.0), once every three months, interim versions with new features (5.1, 5.2, 5.3) and, as needed, corrective updates with bug and vulnerability fixes (5.1. 1, 5.1.2, 5.1.3 .XNUMX).
The interim versions will create functionality for the next major version, that is, MongoDB 5.1, 5.2 and 5.3 will add new functions for the version of MongoDB 6.0.
Regarding the novelties that are presented in this new version of Mongo DB 5.0 We can find that I know added support for API version control, which allows you to bind an application to a specific API state and eliminate the risks associated with a possible backward compatibility violation when moving to new versions of the DBMS. API version control separates the application life cycle from the database life cycle and it enables developers to make changes to the application when the need arises to take advantage of new capabilities, rather than when transitioning to a new version of the database.
Another important novelty are the data collections in the form of time series which are already optimized to store portions of parameter values recorded in certain time intervals (time and a set of values corresponding to this time). MongoDB treats these collections as immaterialized and recordable views created from internal collections and automatically groups time series data into an optimized storage format when inserted.
It also stands out that it was added support for Live Resharding mechanism, which allows you to change the sharding keys used for sharding on the fly without stopping the DBMS.
As well as support for analytical functions that allow you to perform actions with a specific set of documents in a collection. Unlike aggregate functions, window functions do not collapse into a grouped set, but rather aggregate based on the content of a "window" that includes one or more documents in the result set.
In addition, Field encryption capabilities have been expanded on the client sideas you can now reconfigure x509 audit filters and certificate rotation without stopping the DBMS. Added support for configuring the cipher suite for TLS 1.3.
On the other hand, it also stands out in the announcement of this new version that a new command line shell MongoDB Shell has been proposed (mongosh), which is being developed as a separate project, written in JavaScript using the Node.js platform and distributed under the Apache 2.0 license.
MongoDB Shell allows you to connect to a DBMS, change the configuration and send queries. Supports smart autocompletion for MQL expression, command and method input, syntax highlighting, context hints, parse error messages, and the ability to expand functionality through plugins
Of the other changes presented:
- Find, count, different, aggregate, mapReduce, listCollections, and listIndexes are no longer blocked if an operation runs at the same time as it acquires an exclusive lock on a document collection.
- As part of an effort to remove politically incorrect terms, the isMaster command and the db.isMaster () method have been renamed to hello and db.hello ().
- The old "mongo" CLI has been deprecated and will be removed in a future release.
Finally, if you are interested in knowing more about it, you can consult the details in the following link.