What is your process for spinning up development, test or staging environments? If you’re like most, it may be complex and manual. You may be have difficulty simulating production data. If that’s the case, attend our webinar on July 1. We’ll show you how you can quickly spin up new MongoDB environments using MongoDB Management Service.
MongoDB Backup using the MongoDB Management Service provides unlimited restores and a simple process that enables you to quickly and easily deploy new environments from live production data. You can be sure you’re working with the most current data at all times, without affecting your production environment. In addition, the newly released MMS API enables you to programmatically perform restores to automate the process of building new environments.
Ready to learn more?
How to Lower Your MongoDB Backup Bill
Using MongoDB Management Service, you can back up MongoDB with ease and rest assured that you always have a reliable backup. The service is pay-as-you-go based on a combination of snapshot storage and oplog processing fees. We offer a free tier to get you started. To get an idea of what your monthly costs would be, you can hook up monitoring, which is a completely free service, and view an estimate of your monthly bill within MMS. However, that estimate doesn’t tell the full story. There are also two ways that you can further tune your costs. Option 1: Exclude non-critical collections: Not all data is created equal. By excluding collections, your backup and restore strategy – and budget – can center around the mission critical data. Many of our customers chose to exclude their non-critical logging, caching or analytics data from backup. Option 2: Set a custom snapshot schedule and retention policy: By default, MMS takes snapshots every 6 hours, and retains them according to a standard policy (hourly snapshots stored for 2 days, daily snapshots stored for a week, the weekly snapshots stored for a month, monthly snapshots stored for a year). You can also customize both the frequency of the snapshots captured and the length of time that the snapshots are retained in order to further control your costs. Want to learn more about MongoDB backup? Create an account today or contact us to learn more.
How Trust and Collaboration Are Helping Intern Erin McNulty Take On New Challenges
Erin McNulty, a rising senior at Columbia University, is working as a software engineering intern in MongoDB’s New York City office. After interning at MongoDB during the summer of 2021, Erin returned this year to take on a new challenge on a new team — and a new programming language. Read on for more about Erin’s experience and how MongoDB’s engineering culture has enabled her to grow. Sammy Attia: Welcome back, Erin! I know this is your second summer internship at MongoDB. Can you share a bit about why you decided to join MongoDB in the first place and why you decided to come back? MongoDB intern Erin McNulty Erin McNulty: The first time I chose MongoDB, it was because throughout my interview process, I could tell that MongoDB really valued interns’ growth, so I felt like spending my summer here would be a really good investment. I knew that at MongoDB, I would have a meaningful project that truly helped me grow and would make an impact at the company. I also really enjoy the culture of the New York City technology scene, so I was really excited to receive an offer from a company that was created and headquartered in NYC. When I was deciding to come back to MongoDB the second time, I really prioritized working at a place that would let me explore different types of software engineering because I wanted to make the switch from web programming to systems programming. I knew that MongoDB’s supportive, learning-oriented environment would allow me to take that risk of trying something new. In addition, I have become really interested in database technology and took a few classes during my junior year, so I wanted to put that knowledge to use on the server team. It’s great to hear that you are able to explore different types of programming as a MongoDB intern. What does the service architecture team do? My team is responsible for building the “glue” that holds different components of the MongoDB server together. We build internal APIs that simplify intra- and inter-process communication within MongoDB deployments. In practice, this looks like building a lot of libraries that make networking, asynchronous programming, and remote command execution simple for replication, sharding, and other server teams to use. I have really enjoyed working on this team, because our job is basically to write clean, reusable code that makes other developers’ lives easier. I find it really satisfying to refactor messy, one-off pieces of code to use our libraries instead. Considering that you’re a two-time intern, what is your favorite part about MongoDB’s internship program? Interns are given a lot of trust at MongoDB, which allows us to not only learn technical skills, but also develop our working styles and take risks during the internship. As the summer has progressed, I have been given more and more trust in terms of designing my own solutions to issues without obvious solutions. Even if I make a decision that might not be the best way to solve the problem, I am given the space to discover and correct that on my own. Because of this, I feel like the MongoDB internship program has helped me grow as an engineer who is responsible for design and execution, not just as somebody who writes code that I am told to write. In addition, the internship has allowed me to explore different aspects of MongoDB through reading documentation from other teams. I’ve also had the opportunity to have coffee chats with other engineers and look through the codebase overall. This makes me feel like I am really valued as a growing engineer, rather than just somebody who is around to do some extra work for the summer. It sounds as though you’re really enjoying our strong engineering culture and are taking advantage of the resources we provide to interns at MongoDB. Could you speak a little more about the overall culture? The first thing that comes to mind when thinking about MongoDB’s culture is collaboration. Curiosity and intellectual humility are cornerstones of our engineering culture, and that leads to really productive engineering. When discussing technical decisions within my team, it is very common to hear, “I thought X, but after listening to you walk through your thinking, I am leaning toward Y.” The culture makes it feel like everyone can contribute, and that every idea is worth hearing because it will be given a fair shot. I also really like the intellectual curiosity of MongoDB engineers. It seems that everyone has a little side interest in another team’s work, and you frequently hear engineers ask each other questions about the inner workings of their projects. It seems that you've really embraced one of our most important company values, "build together." Do you have any advice for students who might be considering interning at MongoDB? I would encourage students considering a MongoDB internship to try new things when choosing their teams for the summer. The first summer I was here, I wanted to stick with what I knew by working on a team that used React and Java. This summer, I had to learn an entirely new language, C++, in order to work on my team, and I think that I have grown so much through this experience of trying something new in my internship. Interested in opportunities for college students at MongoDB? Find out more .