Here's this week's roundup of news from the MongoDB community.
Gazzang Advice from a Big Data Pro
I Learn As I Go Along MongoDB Aggregating Fractals
MongoHQ MongoDB Data Management
MongoHQ Q&A with Gild
The MongoDB Blog Visualizing Performance Metrics of a Sharded Cluster with One MMS Chart
The MongoDB Blog The 2013 FinTech Hackathon
The MongoDB Blog Meet Dan Pasette: VP of Engineering for the Server Team
OpenLife The Answer to Last Week’s MongoDB Aggregation Challenge
Reverb Partitioning MongoDB Data on the Fly
Vlad Mihalcea NoSQL is Not Just About Big Data
Vlad Mihalcea MongoDB Facts: Lightning Fast Aggregation
Meet Stacy Ferranti: Campus Recruiting and University Relations Manager
We're excited to introduce you to Stacy Ferranti, our Campus Recruiting and University Relations Manager. What is your role at MongoDB? I manage our Campus Recruiting and University Relations program. I recruit current students and recent graduates to join our summer internship or new grad program. I focus mostly on software engineers and tech recruits. Once the interns and new grads arrive, I manage the summer program and new grad rotational program. I liken what I do to the NFL draft: bringing up college kids to the pros. Where were you before MongoDB? Why did you choose to come to MongoDB? I studied International Politics in school and I thought I’d move to DC and change the world. I took a 180 and moved to Hong Kong instead to live abroad and be young and reckless for a while. After coming back to the states I kind of fell into recruiting. Right before I came to MongoDB I worked for Gap Inc. in their Talent Management Department. When I decided to move to New York, I contacted my network here. A few people I knew at Sequoia Capital referred me to MongoDB. The company had about 30 people at the time and the office was small and a bit intimidating. But after my first interview something sparked; I knew this company was going to be huge and I had to be here no matter what. How did you learn how to pitch MongoDB to students and developers after starting? I actually learned a ton from our co-founder and CTO Eliot Horowitz; he took the time to teach me what a database was and how ours was different. I persistently had lunch with our engineers and asked them to tell me about what they did. But I also spent a lot of time researching on Google, and following the philosophy of “fake it ‘til you make it”. What’s your hometown? I’m from a small mountain town in Southern California called Lake Arrowhead, but since I spent so much time in San Francisco, I consider that my second home. Bike or public transportation to work? I take the subway and brave the crowds at both Grand Central and Times Square. I have to put on my game face for every commute: every woman for herself! I have a bad habit of taking cabs when there is any hint of inclement weather. I hate the rain. What’s a typical day (or week) for you? Fall and spring are very busy since I could be at any number of college campuses across the country; I travel a lot during the recruiting seasons. When I’m not travelling, a typical day would start at 6am when I get up to work out. I go back home for a cup of coffee and start checking my emails. Inevitably I get lost in my emails and don’t get to the office until much later than I had planned. Once I’m in the office, I try to practice time blocking. The morning consists of reading student emails (which always seem to be sent between 12 and 4 am) reviewing resumes, and contacting candidates. I’m usually on the phone from 1 to 6 pm or later. In the summers, I spend the entire day running the internship program and planning for the upcoming fall. What’s the most interesting thing you’ve seen on a resume? I’ve seen some pretty interesting stuff on resumes. A lot of chess champions, and body-builders, people doing standup comedy, many people claiming to be connoisseurs of various types of food. What do you love most about MongoDB? I love the collaboration, transparency, and shared interests and passions I have with my co-workers. MongoDB is creating disruptive technology by developers for developers—it’s not social networking or a fleeting technology that no one will have heard of 10 years from now—which is really important to me. And the people I work with are absolutely amazing. What’s the most challenging aspect of your job? In a world of instant gratification, shiny things, and over the top perks at tech companies it’s so challenging to convey what actually matters in life to college students. What’s one of the most rewarding experiences you’ve had working here so far? I love seeing our summer interns turn into full time employees. When they get shout outs in our company-wide emails for the work they do, it puts me on cloud nine and makes all the long hours and travel beyond worth it! What’s your MongoDB kitchen snack weakness? I’m absolutely addicted to Oreos. Can’t stop, won’t stop! Name one secret skill you have, unrelated to work. I am surprisingly good at identifying and imitating American regional accents. My favorite is Minnesotan. Kindle or book? What’s your favorite book? Books. I’m old school. I love just about anything from John Steinbeck or Annie Proulx. But my favorite book is The Story of Edgar Sawtelle. I really enjoy stories about humans being humans, especially when the ending isn’t particularly happy. Describe your perfect weekend. When I romanticize New York, it’s perpetually fall (when I think New York is most beautiful). I’d start with Friday night dinner at my neighborhood Italian spot with nothing to do the next morning. Then I’d get up early and have coffee at home, leave the house with no agenda and get lost in the city. I’d spend the day discovering new neighborhoods, new restaurants, etc. And if it’s football season, it’s football Sunday (49ers all the way!) What’s your favorite cocktail? I’m always in search of the perfect Bloody Mary or Michelada. What ‘s your dream honeymoon? (Stacy is getting married in July!) Ideally somewhere warm and tropical where I would have nothing to do but enjoy the company of my new husband! If you're interested in joining the MongoDB Team there are a number of open positions available in Engineering, Sales, Marketing, and Business Development. To learn more about open roles at MongoDB, please visit the MongoDB Careers Page.
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