Our release this week is a tiny bit delayed, for those of you who are tracking it, due to an internal MongoDB engineering conference. There’s lots going on here at HQ, including but not limited to our upcoming release of MongoDB 2.8 .
As for the MMS release this week, we’ve been very busy:
UI & Core
- Additional API functionality (users can now add host aliases)
- Changes to the settings page - users can now leave a group, add a group, and go to each group via their personal groups list
- Additional instructions for command line for the automation agent. If you’ve never used the command line before, we’ve got you covered. There’s also a fancy copy-to-clipboard widget.
- Ability to define CNAMEs for config servers that are provisioned on own hardware (i.e. where the customer is managing DNS themselves).
- For backup customers, you’ll notice that restore jobs now calculates download/transfer time estimate and displays it in the UI
- New backup and monitoring agents that work with RHEL7
- and the newest version of Monitoring Agent will now send dbStats for all databases, even if you have more than 100 of them!
Check out all these updates and more at mms.mongodb.com !
Part 2: Your App is Taking Off, Now What? It’s Time to Scale Out MongoDB.
In our first post on scaling , we discussed fundamentals of designing a performant and scalable application on MongoDB. Once you’re confident that your application is healthy and ready to grow, it’s time to think about scaling. Before jumping into it, make sure you consider the different ways to scale, and beware of the potential pitfalls: 1. Understand Why You’re Scaling, and What Issues Are Down the Road There are a lot of ways in which an application could be experiencing growth – or constraints to growth! Your workload could be predominantly reads or predominantly writes. Maybe your access operations are under control, but your data volume isn’t. As you grow, you could hit bottlenecks caused by bad schema decisions, inefficient indexing, insufficient RAM, disk speed, network latency, poor planning of transactional vs. analytical queries, or any of dozens of other factors. All of these root causes have different potential solutions. Choosing the right strategy requires understanding your dataset, your users, how you expect to grow, and more. 2. Understand the Trade-Offs: Horizontal vs. Vertical Scaling While MongoDB makes it easy to horizontally scale out with built-in automatic sharding, sharding – or adding more shards – isn't always the only answer. In some cases, making improvements to your hardware can remove constraints that you might be encountering. For example, if your dataset grows and your working set no longer fits in RAM, you might invest in more RAM before deciding to scale out to more machines. Similarly, in some instances, it might make sense to add more or faster disks, or upgrade to SSDs. 3. Choose Your Shard Key Wisely MongoDB supports multiple shard key policies to match your needs. Your shard key selection will impact performance of your cluster. It’s critical that you pick the right key based on your application requirements and expected usage patterns. You want to ensure both even distribution of writes and query isolation – i.e., that queries are targeted to a single shard as much as possible, rather than broadcast (scatter/gather) to all shards. By thinking about these issues before choosing a shard key, you can ensure scalable growth and avoid common sharding pitfalls . So how do I make these decisions about scaling? Take advantage of the many resources we provide. You can start by talking with an expert about scaling strategies for free . When you’re ready to take the next step, our Deployment Topology consulting package is a great way to evaluate your scaling options. And you can always check out our documentation and white papers for more tips.
How the Austin Chapter of MongoDB’s Women’s Group Built Community During the Pandemic
MongoDB is on a mission to create an inclusive workplace where every single employee can thrive. With a range of established affinity groups — and new ones forming regularly — MongoDB looks for ways to amplify those groups’ efforts and help support their overall mission. When the COVID-19 pandemic forced offices to shut down and employees to work from home, our affinity groups were challenged to find creative ways to support and grow their now-remote communities. As leaders of the MongoDB Women’s Group Austin chapter, we share how we pivoted this challenge into an opportunity. First, What's the MongoDB Women's Group The MongoDB Women’s Group is a community of MongoDB employees identifying as women, nonbinary, or trans. Our mission is to create a bold, visible, and united force for gender equality. To help us get there, the MongoDB Women’s Group hosts monthly members-only meetings as well as events open to both members and allies. Relaunched in 2018, the Austin-based chapter connects women and allies in our Austin office to a community of local companies and women’s groups that can support their growth within the tech industry. Pre-COVID, we gained a lot of momentum with our events, which included a live speaker series in the office, yoga, and events focused on subjects such as fertility and imposter syndrome. When COVID-19 hit, we faced a new challenge: how do we create a sense of community for our members when everyone works completely remote? Although initially daunting, the challenge of organizing remote events was an opportunity in disguise. It enabled us to kick off a speaker series for all employees, featuring prominent women in leadership positions across the country. Enter Angie Brown, from The Home Depot. Angie was the first woman to join our remote speaker series, and we couldn’t have asked for a better person to kick it off. She began her career at The Home Depot in 1998 as an entry-level software developer and now is Vice President of Technology — Merchandising, leading a team that develops solutions to support cataloging, pricing, and assortment capabilities at the giant retail chain. She also helps to mentor aspiring leaders in a number of ways, including actively participating in Atlanta’s Women in Technology association. Here, we share some highlights from our fireside chat with Angie during which she discussed her career and provided advice on what women can do to set themselves up for success. Fireside Chat with Angie Brown MongoDB: What advice do you have for those just starting off in their careers? Angie Brown: Opportunities can look like problems and not everyone wants to run into the fire, but avoiding problems can really be a missed opportunity. That’s one important lesson I’ve learned throughout my career. Although you should have a general idea of where you want to go, you also need to be willing to flex. Things might unfold in ways you didn’t expect. If you’re too prescriptive, you might miss out on them. So, you need to find a way to strike a balance. MongoDB: You took a role in leadership fairly early. How did you change your skills and evolve as you moved up? AB: When I talk to people considering moving into management, I ask them to look at the job and determine if the required qualities and responsibilities would make them happy. It’s not just about the title and pay increase. When you pivot from being an individual contributor to being in a leadership role, servant leadership is a huge part of it. If you look at management as a way to control, you won’t be happy. If you look at it as a way to serve others and help them be successful, then you’ll find joy in that career shift. I didn’t prethink this when I first moved into management and had a little bit of an identity crisis. I was used to being the one who got things done. All of a sudden, my role and life was all about going to meetings, and I didn’t look at meetings as tangible work. I was over it. Where was the joy in this? If your joy comes from having your hands on the keyboard and needing to do things your way, then being in management would be like fitting a square peg in a round hole. At first I felt invalidated and unsure of myself because it wasn’t my hands on the keyboard. I had to work through that and do a little soul-searching. I reframed my thinking to be happy leading a team and helping them solve their problems, even if it meant I wasn’t solving them myself. I had a lightbulb moment when I moved into a director role when I realized I was still solving big problems by helping my team tackle them. There’s nothing wrong with where you find your joy and no judgement if your passion aligns as an individual contributor; we need amazing developers! Always be aware of the work itself and make sure it aligns with what you enjoy. MongoDB: How have mentors played a role in your success? AB: I wish I had invested in mentors much sooner. In the early stages of my career, I didn’t think I needed help and believed I could just figure it all out on my own. I thought asking for help was a sign of weakness. In hindsight, my mentors have absolutely formed part of who I am today. I don’t have just one mentor. Instead, I look at a topic and focus on finding a mentor for that specific topic. With that approach, I have ended up having a number of mentors. Thank you again to Angie Brown! We appreciate your insight and inspiration. If you are interested in joining MongoDB, explore our career opportunities and join an innovative team that is disrupting the database industry every day.