MongoDB 3.1.5 has been released. As a reminder, 3.1.5 is a development release and is not intended for production use. The 3.1 series will evolve into 3.2, which will be for production.
New/fixed in this release:
- SERVER-19143 race in setting OpDebug ns can cause invalid BSON to be returned from currentOp command
- SERVER-19135 Tune default cache size settings for WiredTiger
- SERVER-19034 log command failures at level 1
- SERVER-18977 Initscript does not stop a running mongod daemon
- SERVER-18974 dropCollection fails because setShardVersion request is incorrect
- SERVER-18902 Retrieval of large documents slower on WiredTiger than MMAPv1
- SERVER-17254 WT: drop collection while concurrent oplog tailing may greatly reduce throughput TOOLS-16 Mongodump should not use SlaveOk flag by default
As always, please let us know of any issues.
– The MongoDB Team
Changes to MMS: MMS is now MongoDB Cloud Manager
Introducing the new MongoDB Cloud Manager ! Now when you register for an account in MongoDB Cloud Manager (formerly MMS), you immediately enter a 30 day free trial. All the great features of Cloud Manager are enabled during this period. At the conclusion of the 30 day free trial, you will have the option to choose between the Standard Plan or the Free Tier Plan. A note about the differences in the plans: Standard Plan Full History of Your Monitoring Data Automation Free Tier Plan No per-server charge Monitoring data is limited to 5 minute granularity only for previous 24 hours. Automation functionality is not enabled. If you decide to pick the Standard plan before the free 30 day trial is over, you will still get the remaining days of your trial for free. FAQ Are there any changes to backup plans? Backup remains an optional service. Pricing for backup remains exactly the same as before with no changes . You can sign up for our Cloud Backup service whether you choose the Standard or Free Tier Plan. I’m already running MMS Basic or MMS Classic, what happens to my group? Your group will remain in the existing plan that you have today and continue receiving the same functionality. If you wish, you may switch to the new Standard Plan or Free Tier Plan. What are data bearing servers? A “server” means a single virtual machine or physical server running MongoDB that stores data. Config servers, pure arbiters, and servers only running mongos routers do not count. A server is only counted once even if it has multiple data-bearing mongoD processes running on it. You can get this count by going to your “Deployment” tab, changing to the server list view (≡), unchecking “mongos” and “config”, and counting any servers which have at least one non-arbiter process on them. If I decide to stop using Automation, how do I unmanage my group from MMS? Unmanaging will transfer the control of your deployment from MMS back to your servers. Any further changes must be made manually. From your Deployment tab, click the “…” menu at the Replica Set or Sharded Cluster level. Select ‘Remove from MMS’. Can I still choose the MMS Basic plan to get 8 free servers? The MMS Basic plan is no longer available for new groups.
MACH Aligned for Retail (Microservices, API-First, Cloud Native SaaS, Headless)
Across the Retail industry, MACH principles and the Mach Alliance are becoming increasingly common. What is MACH and why is it being embraced for Retail? The MACH Alliance is a non-profit organization fostering the adoption of composable architecture principles. It stands for Microservices, API-First, Cloud-Native SaaS and Headless. The MACH Alliance’s Manifesto is to: “Future proof enterprise technology and propel current and future digital experiences" The MACH Alliance and the creation of this set of principles originated in the Retail Industry. Several of the 5 co-founders of the MACH Alliance are technology companies building for retail use cases: for example commercetools is a composable commerce platform for retail (built completely on MongoDB). MongoDB has been a member of the MACH Alliance since 2020, as an “enabler” member, meaning use of our technology can enable the implementation of the MACH principles in application architectures. This is because a data layer built on MongoDB is ideal as the basis for a MACH architecture. Members of our Industry Solutions team sit on the MACH technology, growth and marketing councils, and actively are involved with furthering the adoption of MACH across the Retail Industry What is MACH, why is it important for retail? The retail industry has long been a fast adopter of technology and a forerunner in technology trends. This is because of the competitive nature of the business leading a drive towards innovation- its vital that retails are able to react quickly to new technologies (e.g. NFTs, VR, AI) to capture market share and stay ahead of the competitors. Retailers have realized that to be able to deliver new and value-add experiences to their customers, they have to cut back on operational overhead that leads to increased cost and build standard functionality that can either be bought or re-used. This is where the benefits of MACH comes in- it's all about increasing the ability to deliver innovation quickly while lowering operational costs & risk. Microservices: An approach to building applications in which business functions are broken down into smaller, self-contained components called services. These services function autonomously and are usually developed and deployed independently. This means the failure or outage of one microservice will not affect another and teams can develop in parallel, increasing efficiency. API-First: A style of development where the sharing and use of the data via API (application programming interface) is considered first and foremost in the development process. This means that services are designed to aid the easy sharing of information across the organization and simple interconnectivity of systems. Cloud-Native SaaS: Cloud-native SaaS solutions are vendor-managed applications developed in and for the cloud, and leveraging all the capabilities the cloud has to offer, such as fully managed hosting, built-in security, auto-scaling, cross-regional deployment and automatic updates. These are a good fit for a MACH architecture as adopting them can reduce operational costs and frees up developers for value-add work like new unique customer experiences. Headless: Decoupling the front end from the back-end so that front ends (or “heads”) can be created or iterated on with no dependencies on the back end. The fact that the layers are loosely coupled decreases time to market for new front ends, and encourages the re-use back-end services for multiple purposes. It also de-risks change in the long term as services can function independently. Where does MongoDB come in? MongoDB is an enabler for MACH, meaning that using MongoDB as your data layer helps retailers and retail software companies. achieve MACH compliance. Our data model, architecture and functionality empower IT organizations to build in line with these architecture principles. During a digital transformation, where a retailer is modernizing a monolith into a microservices based architecture, they're looking for a data layer which will enable speed of development & change. MongoDB is the "most wanted" database 4 years running on Stack Overflow's developer survey- this is because our document model maps to the way developers are thinking & coding, and the flexibility allows for iterative change of the data layer. When looking at API based communication, the standard format for APIs is JSON, which again maps to MongoDB's document model. The idea with API-first development is to develop with the API in mind- why not store the data the way you're going to serve it by API. This reduces complexity and increases performance. Cloud Native and SaaS products have become the norm as retailers wish to reduce maintenance and management work. MongoDB Atlas, provides a database-as-a-service, guaranteeing 99.995% uptime, automatic failover and self-healing and allowing DevOps engineers to spin up databases in minutes or by API/ script. Many retail software companies are also built on MongoDB Atlas- for example commercetools, which provides an ecommerce solution as a SaaS product. Headless architectures require a data layer that is able to adapt and change for new workloads. The ability to change the schema at runtime, with no downtime, makes MongoDB's document model ideal for this. Performance and the ability to scale for new "heads" is also important. MongoDB is known as a high performance database and can scale vertically automatically or scale out horizontally seamlessly. So MongoDB becomes a great choice for retailers choosing to adopt a MACH architecture (see figure 1 below). As a general purpose database with high performance, a rich expressive query language and secondary indexing, MongoDB is a really good fit as a data layer as it is capable of handling operational and analytical needs of the application. FIgure 1: Example of a MACH architecture Want to know more? Are you interested in a transition to MACH? Dive into our four part blog series exploring each topic in detail and how MongoDB supports each of these principles: Microservices API-First Cloud-Native SaaS Headless