MongoDB 3.6.0-rc0 is released

MongoDB
October 20, 2017 | Updated: December 13, 2017
#Community#Company

MongoDB 3.6.0-rc0, the first release candidate of MongoDB 3.6, is out and is ready for testing. This is the culmination of the 3.5.x development series, and includes many exciting new features. Here are some of the highlights:

Fully Expressive Array Updates

This feature, the most voted by the MongoDB user community, enables developers to perform complex array manipulations against matching elements of an array, including elements embedded in nested arrays, all in a single update operation. Fully expressive array updates allows even more flexibility in data modeling.

More Expressive Query Language and Aggregation Pipeline

New aggregation operators and the ability to use aggregation expressions within the query language enable richer queries with less client-side code. This enhancement allows the referencing of other fields in the same document when executing comparison queries, as well as powerful expressions such as multiple JOIN conditions and uncorrelated subqueries. Other Aggregation Pipeline improvements include support for timezone-aware aggregations, conversion of objects to arrays and arrays to objects, and many more.

Retryable Writes

This feature moves the complexity of handling temporary system failures from the application to the database. Developers no longer need to implement custom, client-side code -- the MongoDB driver can automatically retry writes in the event of failure, while the MongoDB server enforces exactly-once processing semantics.

Change Streams

Change streams enable developers to build reactive, real-time, web, mobile, and IoT apps that can view, filter, and act on data changes as they occur in the database. Change Streams enable seamless data movement across distributed databases, making it simple to stream data changes and trigger actions wherever they are needed.

Tunable Consistency

With tunable consistency, MongoDB affords developers precise control over routing queries across a distributed cluster, balancing data consistency guarantees with performance requirements. MongoDB 3.4 added linearizable reads, which were central to MongoDB passing Jepsen tests – some of the most stringent data safety and correctness tests in the database industry. MongoDB 3.6 introduces additional consistency controls: “Causal Consistency” and “Consistent Reads”.

Schema Validation

Schema Validation via syntax derived from the proposed IETF JSON Schema standard extends the capabilities of document validation, originally introduced in MongoDB 3.2.

End-to-End Compression

Wire protocol compression of network traffic between the client and the database, configured with the snappy or zLib algorithms, allows up to 80% savings in network bandwidth. This reduction brings major performance gains to busy network environments and reduces connectivity costs, especially in public cloud environments, or when connecting remote assets such as IoT devices and gateways.

Extending Security Controls and IP Whitelisting

MongoDB 3.6 will, by default, reject all network connections to the database unless explicitly configured to allow them by an administrator. Combined with the new IP Whitelisting feature, administrators can configure MongoDB to only accept external connections from approved IP addresses or CIDR ranges that have been explicitly added to the whitelist.

MongoDB 3.6 Release Notes | All 3.6.0-rc0 Issues | Downloads

As always, please let us know of any issues.

-- The MongoDB Team

← Previous

A Founder’s Reflections on 10 Years of MongoDB

Today is the 10 year gitaversary of mongodb , and it is also the day that we become a publicly traded company. A coincidence, but fun regardless. When Dwight and I started working on the project that would become MongoDB ten years ago, we definitely did not imagine that we would be where we are today. We only had our belief that we could make developers more productive. MongoDB was born out of our frustration using tabular databases in large, complex production deployments. We set out to build a database that we would want to use, so that whenever developers wanted to build an application, they could focus on the application, not on working around the database. Databases are large and complex pieces of software. We would never have gotten to where we are today without an absolutely tremendous team, incredible customers, and a community that both supports us and holds us accountable to be as good as we can be. While thanking each and every person who helped us would be impossible, what I can do is promise to continue making MongoDB the best it can be, so that you can focus on building great applications, and leave the data management nonsense to us. About the Author Eliot Horowitz is the CTO and Co-Founder of MongoDB. He wrote the core code base for MongoDB starting in 2007, and subsequently built the engineering and product teams. Today, Eliot oversees those teams, and continues to drive technology innovations at MongoDB. Prior to MongoDB, Eliot co-founded and built ShopWiki, a groundbreaking online retail search engine. He built its technology, it’s team, and presided over its private sale in 2010. Before that, Eliot was a software developer in the R&D group at DoubleClick. Eliot is on the board of the NY Tech Talent Pipeline. In 2006, he was selected as one of BusinessWeek’s Top 25 Entrepreneurs Under Age 25, and in 2015 was named to the Business Insider “Under 35 and Crushing it” list. He was also recently named to Crain’s NY Business 40 Under 40 Class of 2017 list. Eliot received a B.S. in Computer Science from Brown University.

October 19, 2017
Next →

Data and the European Landscape: 3 Trends for 2022

The past two years have brought massive changes for IT leaders: large and complex cloud migrations; unprecedented numbers of people suddenly working, shopping and learning from home; and a burst in demand for digital-first experiences. Like everyone else, we are hoping that 2022 isn’t so disruptive (fingers crossed!), our customer conversations in Europe do lead us to believe the new year will bring new business priorities. We’re already noticing changes in conversations around vendor lock-in, thanks to the Digital Markets Act, a new enthusiasm for combining operational and analytical data to drive new insights faster, and a more strategic embrace of sustainability. Here’s how we see these trends playing out in 2022. Digital markets act draws new attention to cloud vendor lock-in in Europe We’ve heard plenty about the European Commission’s Digital Markets Act , which, in the name of ensuring fair and open digital markets, would place new restrictions on companies that are deemed to be digital “gatekeepers” in the region. That discussion will be nothing compared to the vigorous debate we expect once the EU begins the very tricky political business of determining exactly which companies will fall under the act. If the EU sets the bar for revenues, users, and market size high enough, it’s possible that the regulation will end up affecting only Facebook, Amazon, Google, Apple, and Microsoft. But a European group representing 2,500 CIOs and almost 700 organizations is now pushing to have the regulation encompass more software companies. Their main concern centers around “distorted competition” in cloud infrastructure services and a worry that companies are being locked into one cloud vendor. A trend that will likely increase in 2022 that pushes back on cloud vendor lock-in is embracing multi-cloud strategies. We should expect to see more organisations in the region pursuing multi-cloud environments as a means to improve business continuity and agility whilst being able to access best of breed services from each cloud provider. As we have always said …”it’s fine to date your cloud provider….but don’t ever marry them.” The convergence of operational and analytical data The processing of operational and analytical data is almost always contained in different data systems, each tuned to that use case and managed by separate teams. But because that data lives in separate places, it’s almost impossible for organisations to generate insights and automate actions in real time, against live data. We believe 2022 is the year we’ll see a critical mass of companies in the region make significant progress toward a convergence of their operational and analytical data. We’re already starting to see some of the principles of microservices in operational applications, such as domain ownership, be applied to analytics as well. We’re hearing about this from so many of our customers locally, who are looking at MongoDB as an application data platform that allows them to perform queries across both real-time and historical data, using a unified platform and a single query API. This results in the applications they are building becoming more intelligent and contextual to their users, while avoiding dependencies on centralized analytics teams that otherwise slow down how quickly new, data-driven experiences can be released. Sustainability drives local strategic IT choice Technology always has some environmental cost. Sometimes that’s obvious — such as the energy needs and emissions associated with Bitcoin mining. More often, though, the environmental costs are well hidden. The European Green Deal commits the European Union to reducing emissions by 55% by 2030, with a focus on sustainable industry. With the U.N. Climate Change Conference (COP26) recently completed in Glasgow, and coming off the hottest European summer on record, climate issues have become top of mind. That means our customers are increasingly looking to make their technical operations more sustainable — including in their choice of cloud provider and data centers. According to research from IDC , more than 20% of CxOs say that sustainability is now important in selecting a strategic cloud service provider, and some 29% of CxOs are including sustainability into their RFPs for cloud services. Most interesting, 26% say they are willing to switch to providers with better sustainability credentials. Historically, it’s been difficult to make a switch like that. That’s part of the reason we built MongoDB Atlas — to give our customers the flexibility to run in any region , with any of the three largest cloud providers, and to make it easy to switch between them, and even to run a single database cluster across them. Publicly available information about the footprint of individual regions and even single data centers will make it simpler for companies to make informed decisions. Already, at least one cloud platform has added indicators to regions with the lowest carbon footprint. Source: IDC, European Customers Engage Services Providers at All Stages of Their Cloud Journey, IDC Survey Spotlight, Doc #EUR248484021, Dec 2021

December 21, 2021