MMS OnPrem 1.4.2 Release Notes

MongoDB
June 2, 2014
#Cloud

Several weeks ago, the MongoDB Management Service launched OnPrem 1.4 with Backup. MMS OnPrem is the self-hosted sibling to our cloud product, packaged up into a service that customers can run within their own private environment. On May 29th, we released OnPrem 1.4.2, which contains some small changes geared toward the requirements of our enterprise customers. Specifically:

One critical bug fix for backing up MongoDB 2.6 deployments that include user or custom role definitions, where the system.version collection in the admin database will be included in all future snapshots and the system.roles collection in the admin database will be included after a new initial sync is performed.

Users capturing backups with MMS of MongoDB 2.6 replica sets or clusters that include custom role definitions should perform a new initial sync to ensure that the role definitions are included in the backup. Disable MongoDB usePowerOf2Sizes for insert-only MMS Backup collections.

Speed optimization for MMS Backup HTTP pull restores.

A fix for LDAP integration, MMS now passes full dn correctly when authenticating the user.

MMS OnPrem provides an easily integrated backup solution for MongoDB in house, providing point-in-time recovery for replica sets and cluster-wide snapshots of sharded systems. MMS OnPrem is included as part of our MongoDB subscription.

Found an issue or a bug or a have a feature request? File a ticket in our feature request queue!

-Rachelle (@techbelle)

← Previous

MongoDB Performance Tuning and Monitoring with MMS

In a recent webinar, MongoDB Technical Services Engineer Daniel Coupal presented on how you can use MMS for performance tuning and monitoring. He explains which metrics to examine when optimizing your MongoDB deployment. Daniel and the MongoDB Technical Services team work with thousands of MongoDB customers and community users each year, and drawing from those experiences Daniel also provided several real-world examples of diagnosing and debugging performance issues with the MongoDB Management Service. You can watch the full video below. Monitoring is completely free with MMS. Why not give it a try? Create your free account today.

June 2, 2014

Next →

The Rise of the Strategic Developer

The work of developers is sometimes seen as tactical in nature. In other words, developers are not often asked to produce strategy. Rather, they are expected to execute against strategy, manifesting digital experiences that are defined by the “business.” But that is changing. With the automation of many time-consuming tasks -- from database administration to coding itself -- developers are now able to spend more time on higher value work, like understanding market needs or identifying strategic problems to solve. And just as the value of their work increases, so too does the value of their opinions. As a result, many developers are evolving, from coders with their heads-down in the corporate trenches to highly strategic visionaries of the digital experiences that define brands. “I think the very definition of ‘developer’ is expanding,” says Stephen “Stennie” Steneker, an engineering manager on the Developer Relations team at MongoDB. “It’s not just programmers anymore. It’s anyone who builds something.” Stennie notes that the learning curve needed to build something is flattening. Fast. He points to an emerging category of low code tools like Zapier, which allows people to stitch web apps together without having to write scripts or set up APIs. “People with no formal software engineering experience can build complex automated workflows to solve business problems. That’s a strategic developer.” Many other traditional developer tasks are being automated as well. At MongoDB, for example, we pride ourselves on removing the most time-consuming, low-value work of database administration. And of course, services like GitHub Copilot are automating the act of coding itself. So what does this all mean for developers? A few things: First, move to higher ground. In describing one of the potential outcomes of GitHub Copilot, Microsoft CTO Kevin Scott said, ““It may very well be one of those things that makes programming itself more approachable.” When the barriers to entry for a particular line of work start falling, standing still is not an option. It’s time to up your strategic game by offering insight and suggestions on new digital experiences that advance the objectives of the business. Second, accept more responsibility. A strategic developer is someone who can conceive, articulate, and execute an idea. That also means you are accountable for the success or failure of that idea. And as Stennie reminded me, “There are more ways than ever before to measure the success of a developer’s work.” And third, never stop skilling. Developers with narrow or limited skill sets will never add strategic value, and they will always be vulnerable to replacement. Like software itself, developers need to constantly evolve and improve, expanding both hard and soft skills. How do you see the role of the developer evolving? Any advice for those that aspire to more strategic roles within their organizations? Reach out and let me know what you think at @MarkLovesTech .

July 29, 2021