January 2020 Summaries

As a Senior Solutions Architect at MongoDB, Veronica Tudor has experienced growth both personally and professionally. She joined MongoDB 2+ years ago primarily due to its innovative technology in the database space. Over time, she discovered that the company's culture and people also play a significant role in her job satisfaction. Recently, Veronica took parental leave for the birth of her second child and is now returning to work with a new perspective on balancing personal and professional life. In her current role, Veronica works closely with customers, including C-level executives and developers, to understand their needs and provide solutions that meet their objectives. She has grown professionally by mastering context switching and staying up-to-date with the latest technologies in the industry. With MongoDB's supportive culture and resources, Veronica feels excited to continue growing both personally and professionally as a Solutions Architect.

MongoDB is a popular NoSQL database that requires careful data modeling and memory sizing to achieve optimal performance, especially when dealing with large datasets and high traffic. To design an efficient data model, developers should consider how to embed or reference related data within documents, taking into account factors such as document size limits, query patterns, and application-specific requirements. A well-designed data model can improve query performance, reduce the need for disk reads, and optimize storage usage. Additionally, MongoDB Atlas provides a managed cloud database service that allows developers to easily scale their instance sizes based on their working set size, ensuring that the application's frequently accessed data fits within RAM. By following best practices for data modeling and memory sizing, developers can improve the performance of their MongoDB applications and achieve better scalability and reliability.

George Wangensteen is a rising senior at Brown University studying Computer Science who spent his summer as a Software Engineering Intern on MongoDB's Query team. He worked on the core database product, optimizing query execution and plan generation for user queries. Wangensteen enjoyed working on aggregation pipelines running against sharded collections and appreciated the culture at MongoDB, which encouraged asking questions and learning from experts. The internship provided him with hands-on experience in a new programming language, C++, and helped him improve his skills as an engineer through mentorship and challenging projects.

Meet Matt Kalan, Master Solutions & Enterprise Architect at MongoDB, who has worked at the company for over 7 years. The role of a Solution Architect (SA) at MongoDB is unique due to its focus on understanding customer goals and architecting solutions on top of MongoDB, rather than just demonstrating pre-made applications. This requires SAs to be broadly knowledgeable about various technologies and have a consistent focus on qualifying customers' situations before providing demos. In his 7+ years at MongoDB, Matt has made an impact by creating marketing content, running enablement sessions for the Central US teams, and sharing customer feedback with product teams. As a leader in the SA team, he has opportunities to build a career path, whether as an individual contributor or people manager, and is involved in quarterly leadership meetings and informal roundtables among the SA team. The relationship between Sales and SAs at MongoDB is collaborative, with mutual respect and a balancing dynamic between the two teams. Matt joined MongoDB 7 years ago due to its hot area of technology, Big Data, and has grown both personally and professionally in his role, with much more growth potential ahead.

As an engineering intern on MongoDB's Driver team, Sam Pal worked on the Node.js driver, programming in Node.js to maintain the driver and implement new features. Her team interacted with users to understand their needs and address issues, and she learned big-picture skills like creating a proof-of-concept and GitHub tips and tricks. The culture at MongoDB is open to idea-sharing, feedback, and growth, with employees dedicated to the product's impact. Sam found the work challenging but rewarding, learning about MongoDB development, Node.js, and the driver's testing stack. Her favorite part was being surrounded by a talented and fun-loving team, with a commitment to excellence that inspires her.

At MongoDB, Julia Prause, Global Director of Customer Success, shares insights into their company's approach to hiring and recruiting top talent for Customer Success (CS) roles. The team looks for candidates who demonstrate excitement for the company and its products, with a focus on career progression, clarity of information, and applicable experience and skills. The hiring process involves multiple stages, including a recruiter screen, a call with the hiring manager, a peer interview, an onsite "challenge" where candidates present a mock onboarding meeting with a new MongoDB customer, and finally, a demo of Atlas, their database-as-a-service in the cloud. Julia offers tips for success in the challenge step, emphasizing the importance of preparation, research, and time management. The company values passion, innovation, and professional development, making it an attractive opportunity for those looking to advance their careers in Customer Success.

Here's a neutral and interesting 1-paragraph summary of the text: This tutorial covers the deletion of documents from a MongoDB collection using the Go programming language. To delete a single document, the DeleteOne function can be used with a filter to specify which document should be deleted, while the DeleteMany function can be used to remove multiple documents in a single operation. Additionally, entire collections can be dropped without using a filter, removing all documents and metadata. The tutorial assumes that the reader has already set up their MongoDB cluster and Go application, and provides examples of how to use these functions to delete documents from two example collections: podcasts and episodes.

Keyhole is a tool used to monitor MongoDB clusters by integrating with Grafana and analyzing Full Time Diagnostic data (FTDC) metrics. It helps identify performance bottlenecks in MongoDB clusters, including WiredTiger tickets, disk IOPS, CPU usage, replication lags, and slow operations from logs. Keyhole can be integrated with Grafana as a SimpleJson Datasource to display FTDC metrics visually, making it easier to diagnose cluster health issues. By analyzing FTDC data and mongo logs, Keyhole provides insights into potential problems such as running out of read or write tickets, disk performance issues, and slow database operations. The tool can also be used to verify new installations, collect MongoDB cluster information, and visualize resource usages in a snapshot.