MongoDB 3.6 will be generally available in early December.
The open source (at its core) general purpose database has some noteable changes (its makers would call them enhancements) including a so-called ‘change streams’ feature, which enable developers to build what are being described as more ‘reactive’ web, mobile and IoT applications that can view, filter and act on data changes as they occur in the database.
By submitting your personal information, you agree that TechTarget and its partners may contact you regarding relevant content, products and special offers.
Whenever data is changed in MongoDB, the updates are automatically reflected (in real time) in the application that the database itself is serving.
The speed of data
For example, a weather application that pulls from constantly changing datasets (as the weather shifts) would have previously required a developer to write application code that periodically polls the database for updates, limiting the application’s ability to provide an accurate, real-time user experience.
Change streams automates that process — this then, is the ‘speed of data’, that is – the velocity at which real world ‘things’ change data in databases serving applications.
(1) always on & (2) distributed
President and CEO of MongoDB Dev “please pronounce my name Dave” Ittycheria insists that MongoDB 3.6 makes it easier (and faster) to build always-on applications that react in real time to changes in data streamed across distributed systems.
That’s the message for cloud apps for sure now then i.e. (1) always on & (2) distributed
“MongoDB has always aimed to make developers more productive by giving them the most friction-free means of working with data,” said Eliot Horowitz, CTO and co-founder, MongoDB. “With advancements like change streams and retryable writes, MongoDB 3.6 handles critical tasks at the database layer that used to take up developer time and energy. Extensions to the query language make array updates and joins more expressive, and new security features curb the possibility of MongoDB instances being left mistakenly exposed.”
Readers will note that the above mentioned ‘retryable writes’ move the complexity of handling systems failures from the application to the database. Instead of developers having to implement custom, client-side code to handle network errors during updates, MongoDB automatically retries writes.
Navigating schema, with a compass
Other noted features include MongoDB Compass, which allows users to analyse and understand database schema.
Compass now includes query auto-complete, query history and table views.
For users who are looking for other features, the new Compass Plugin Framework gives them the power to build and distribute plugins to make MongoDB Compass their ideal navigation tool.
Also of note in the forthcoming release, MongoDB Ops Manager (which allows users to manage, optimize, secure and back up globally distributed clusters) now has a new Data Explorer, Real-Time Performance Panel and Performance Advisor.
Ops Manager 3.6 makes it easier than ever for ops teams to inspect and improve database performance in real time.
A new dimension of agility
“Agility is expressed both in terms of speed… and in terms of flexibility in handling various data formats and volumes, as well as speed in terms of application innovation. Often, one’s data management technology is an inhibitor in both regards. MongoDB 3.6, with its features that address both dimensions of agility as well as increasing demands for better security and geographic flexibility, is well poised to power the functionality that will make enterprises winners in this digitally driven economy,” said Carl Olofson, research vice president for data management software at IDC.
Schema governance with JSON schema lets developers and ops teams combine the flexibility of the document model with data conformance and validation capabilities to precisely the degree that best suits their application.
Because schema validation is fully tunable, teams can add pinpoint validation to only the critical fields of their model, or start a project with data governance appropriate to the development stage and tighten them during production stages. Now teams can benefit from the ease of development that the document model offers, while still maintaining the strict data governance controls that are critical for applications in regulated industries.