By now you surely know that MongoDB 3.6 Community became generally available on Dec 5, 2017. Of course, this is great news: it has some big ticket items that we are all excited about! But we need to talk about general thoughts on this release good an
It is always a good idea for your internal teams to study and consider new versions. This is crucial for understanding if and when you should start using it. After deciding to use it, there is the question of if you want your developers using the new features (or are they not suitably implemented yet to be used)?
So what is in MongoDB 3.6 Community?
- Change streams
- Retryable writes
- Security improvement
- Major love for arrays in aggregation
- A better balancer
- JSON Schema validation
- Better time management
- Compass is community
- Major WiredTiger internal overhaul
As you can see, this is an extensive list. But there are 1400+ implemented Jira tickets just on the server (not even in the WiredTigers project).
This is a big so come hungry!
David is the Practice Manager for MongoDB at Percona. Prior to that he was one of the early memeber for ObjectRocket the leader in DBaaS for MongoDB specializing in performance. Prior to this he was a Database Architect as Electronic Arts , the game producer and help various systems, networking and development roles. His work includes things like sharding, distributed systems, tool building, very large-scale issues, and high-performance MongoDB architecture and design. As a speaker, he prefers to focus on solutions in the real world to issues, to this point he tries to regularly publish code to help everyone use his solutions or have ideas to inspire their own.Additionally, he is a Mongo Master Alumni and core code contributor to MongoDB and other open source technologies.