MongoDB.live Returns this Summer
June 1, 2021 | Updated: June 3, 2022
MongoDB.live is returning in July! Join us for the all-virtual, all-encompassing conference on the future of data.
As the signature convention of the world’s most wanted database, MongoDB.live has something for everyone. Explore current trends and upcoming technologies, build key skills, and connect with other data enthusiasts of all levels and interests.
What's in Store?
This free event will run from July 13-14, and will include engaging presentations, immersive tutorials, interactive discussions, and much more. Whether you’re a DevOps engineer or a solutions architect, you’ll find plenty of useful, engaging, and enlightening content.
On Day 1, kick off MongoDB.live with an exciting keynote headlined by MongoDB executives, experts, and users, who will introduce MongoDB 5.0, and walk you through the latest product announcements — and how these new features will transform how you work with data.
Day 2 will commence with a roundtable panel of MongoDB power users, who will share helpful tips stemming from their own experiences, and discuss how MongoDB solutions have helped their progression to the Cloud and to SaaS.
Both days will feature dozens of educational breakout sessions, deep-dive tutorials for everything from serverless to sharding, live “Ask Me Anything” panels with MongoDB experts and executives, and much more.
What Happened Last Year?
In 2020, MongoDB.live went online for the first time.
During the keynote, Sahir Azam, our Chief Product Officer, explained how the MongoDB team integrated every feature into a seamless, holistic platform that addresses any data need a developer may have.
To demonstrate the MongoDB platform in action, Sahir invited the marine program team from WildAid, a leading global conservation nonprofit, onto the (virtual) stage. WildAid spoke about their mission of protecting vulnerable aquatic ecosystems, gathering vital data, and ensuring compliance with a dizzying array of regulations — and how they used everything from Realm to Atlas Search, to support their operations.
Participants also attended breakouts, talks, and tutorials, including practical advice for building a non-linear career from Capitol Hill to coding; a discussion on open sourcing mentorship; and a walkthrough on building a serverless app with MongoDB Atlas, Realm, and AWS; to name a few.
Lastly, we recognized our 2020 Innovation Award winners, and highlighted MongoDB users and customers who were doing groundbreaking work in their fields. The list of recipients boasts household names like Toyota and Pizza Hut alongside smaller, equally savvy organizations such as Zinc and dacadoo.
How to Join
Please register today to reserve your spot. As we get closer to the event, you’ll receive a confirmation email with instructions to create your profile — which you can use to bookmark sessions and tracks, and fill in your personal details for networking.
During the week before the event, you’ll also be able to access our digital Partner Pavilion and its resources, including entry-level talks, downloadable materials, sponsor booths, and more. On the days of the conference, you can access MongoDB.live from your desktop or mobile device.
As we get closer to MongoDB.live, keep checking the event website, which will be regularly updated with information on workshops, speakers, and what to expect. We can’t wait to see you (virtually)!
Celebrating 10 Years of Interns: A Look Back at MongoDB's Internship Program Over the Years
This summer marks the 10 year anniversary of MongoDB’s internship program. What started as a small experiment with a few interns has grown into a programmatic machine responsible for a third of our engineering hiring. In the past 10 years, we have expanded from New York City to Austin, San Francisco, Dublin, Sydney, Copenhagen, and India. We’ve grown from only engineers, to also hiring Product Managers, Designers, Data Scientists, Marketing roles, and more. In celebration of this historic milestone, we’re taking a look back at how it all started and highlighting an intern from each graduating class along the way. The history of the program is long and winding, but the results are critical to achieve the growth that MongoDB has seen in recent years. The Beginning MongoDB’s internship program began when co-founder Eliot Horowitz, now Executive Vice President of Core Engineering Dan Pasette, now Vice President of Program Management Ian Whalen and the only recruiter on the team at the time, Stacy Ferranti, decided to hire some interns in 2011. When Ian first joined the company, he lent a helping hand to anything and everything, even when it was outside of his core job responsibilities, which led to his involvement in running our first intern program. “The startup life is about doing all of the things,” Ian said. He attended career fairs, helped schedule interviews, and matched interns with mentors. Now, we have an entire Campus Team dedicated to that! Dan Pasette, remembers being active in recruitment as well. Dan drove to universities to give talks and encouraged others to do the same at their own alma maters. “We didn’t have a lot of people dedicated to the program and we experimented with a lot of things along the way,” Dan shared. The beginning days mirrored the life of a startup. Through the years iterations were made, feedback was incorporated, and the program grew not only in size but also in quality. However, two things remained the same through my interviews with our former interns. First, MongoDB always makes sure interns work on interesting challenges. And second, the people at MongoDB genuinely care about each other. Hear from our Former Interns Who Still Work at MongoDB Randolph Tan Intern Class: 2011 University: NYU Current Title & Team: Staff Engineer, Sharding Randolph joined our inaugural intern class and has worked at MongoDB ever since. An engineer from MongoDB came to NYU to give a talk and from there, Randolph got to work on an open source project with the company as a part of a computer science club on campus.. At the end of the semester, he submitted his resume for an internship and got accepted into the program. After his internship, he decided to come back as a full-time employee. “In the beginning, I wasn’t working on an official team, but working on side projects,” Randolph remembered. He worked on a special project with Dan, and then ultimately was adopted into the Sharding team, where he is currently a Staff Engineer today. Back then, Randolph recalls a lack of structure in the program but now says “the structure today gives [an intern] the understanding of what your actual work is going to be and how you interact with the team.” Wisdom Omuya Intern Class: 2012 University: American University of Nigeria & Columbia Current Title & Team: Director of Engineering, Atlas Data Lake Wisdom first came to know MongoDB when Ian attended a career fair at his university. MongoDB ended up being Wisdom’s first and only internship, and clearly it made an impression. After his internship, he joined our New Grad rotation program. At MongoDB, New Grads have the opportunity to rotate on three teams and then choose one of them that is best suited for their skills and interests. Wisdom has remained very close to both the internship and New Grad programs throughout the years. Wisdom attributes many of his successes as now a Director of Engineering to what he learned while mentoring other MongoDB interns. “The experience helped me learn how to support people, especially those coming from a position where they might not have as much confidence in their abilities or the confidence that their skills warrant,” he shared. “Supporting interns, nurturing their talents and helping them with opportunities to thrive is quite fulfilling.” Esha Maharishi Intern Class: 2013 & 2014 University: Columbia Current Title & Team: Director of Engineering, Server Like Randolph and Wisdom, Esha learned about MongoDB when employees visited her school for a career fair. “It sounded like there would be a chance to work on a lot of interesting algorithms,” Esha recalls. She interned twice on the distributed systems team and worked on that team for 5 years after graduation. One of her favorite parts of working at MongoDB was the reading group that was held every other week. “I loved hearing the conversation and understanding more about the field. It was amazing to me that MongoDB had adopted Raft, a replication protocol that had just been published in 2013.” She continued to participate in and lead learning initiatives throughout the years, from hosting a talk on how to find good resources to keeping a shared list of books and papers with engineers’ thoughts on them. She more recently has spent time working on a more research-oriented team, where reading research papers together has been a core part of the work. “It’s still one of the best parts of the week, when we get together and figure out what parts we didn’t understand, what insights we had, and what ideas we can apply to our own work.” Kyle Suarez Intern Class: 2014 University: Rutgers Current Title & Team: Lead Software Engineer, Query Kyle began his journey with MongoDB as an intern on the Drivers Team. His intern project, Monary, was a success and he and his intern partner were invited to speak about it at the PyGotham conference in New York at the end of the summer. After finishing the internship, Kyle went through the New Grad rotation program and ultimately landed on the Query. After three years on the team, he had what he calls an "existential crisis". Unsure of his career path, he decided to leave the company and work in finance. But he couldn't stay away for long -- after a two year hiatus, one of his MongoDB intern buddies called him up and told him about a Lead Engineer opportunity on the Query Team. "I was unsure of whether or not to come back, but I was excited to hear about the company's growth. Most of all, I realized that I missed my friends at MongoDB and the friendly engineering community they had built." Kyle rejoined the company in 2021, leading a team on Query Execution. He says that working as a lead has been very satisfying. "MongoDB definitely builds lots of cool features, but this is a lot more than that. Supporting the team and helping them develop their own careers as engineers brings me a great sense of joy and fulfillment." Emily Pakulski Intern Class: 2015 University: Columbia Current Title & Team: Tech Lead, Cloud Insights & Telemetry Kyle is not the only person to have left MongoDB and come back! Emily, a HackNY fellow, interned with MongoDB in the Summer of 2015 on the Cloud Automation team. She first learned about MongoDB through a hackathon, and then discovered several of her most talented friends and Teaching Assistants joined as New Grads here. While she had a great time during her summer internship, she later attended a startup fair and became very passionate about the startup world. “I really wanted to do something mission oriented,” Emily remembers, “and that led me to go to a little, little startup.” Through this new job, Emily was able to travel to Niger (in West Africa), a highlight of her early 20s. While the experience was amazing, she began to realize that she wasn’t on track to reach her full potential by developing core technical skills. She met up with one of her former TAs who had been at MongoDB since graduating, Jonathan Balsano, and they discussed the kind of technical challenges that might be available back at MongoDB. She matched with the Cloud Backup team. “It was very obvious that MongoDB was the right fit. Everything I didn’t have at the startup, I had on the Backup team. It was interesting, backend work, focused on technical problems and much more team-oriented.” Years later, Emily now is on Jonathan’s team, and has grown to be an engineering manager herself. Marcus Todd Intern Class: 2016 & 2017 University: Carnegie Mellon Current Title & Team: Software Engineer, Realm Marcus learned about MongoDB the way many of our former interns do, recognizing our super comfortable t-shirts on campus. I met Marcus at a career fair in 2015 and he joined us for the Summer of 2016 on the Cloud Core team and the Summer of 2017 on the Drivers team. Marcus enjoyed the breadth of work available here. “Before the internship, I [assumed] everyone was going to be doing database work, but as an intern I learned [MongoDB] is way bigger than I had expected.” The decision for him to join as a New Grad was an easy one, and enjoyed the opportunity to rotate on even more teams within the company. Ultimately, Marcus landed on Stitch, which later became Realm after an acquisition. Realm feels like a startup within a startup, which has been the most exciting part of Marcus’s journey at MongoDB. “It’s funny because it’s only been three years, and we will take a look at the code base and some of it looks like ancient runes. But I remember, I may have written some of those myself.” Marcus also has been a mentor for several interns and New Grads, and enjoys the opportunity to meet unique individuals and help them grow. Tyler Kaye Intern Class: 2017 University: Princeton Current Title & Team: Software Engineer, Realm Tyler interned with Marcus in 2017, and also joined the Realm team after graduation. However, his journey is a bit different. Tyler was originally an intern on the Server team, and was working on a mobile project. “I interned on the Service Architecture team working on the POC for Embedded MongoDB, which is kind of the precursor to MongoDB Sync,” Tyler explained. “I think I get to say that my phone was the first phone to ever run MongoDB.” Tyler completed his rotations and joined the Stitch team in 2018 working on MongoDB Sync, and then a few months later Realm was acquired. Realm was based out of Copenhagen, so there was a concern that “some people in Copenhagen would have to move to New York or some people in New York to move to Copenhagen, and I went to my manager and said, I am happy to move to Copenhagen. My manager approved, and I relocated!” While living in Copenhagen, Tyler was able to travel around Europe and experience a brand new culture, while still working on the product he loved. The pandemic shortened his timeline abroad a bit, but certainly did not slow down the growth of Realm. “Four or five months ago, our team was three people and now we are eight,” Tyler told me. Both Tyler and Realm don’t seem to be slowing down any time soon. Allison Mui Intern Class: 2018 University: Carnegie Mellon Current Title & Team: Product Designer, Documentation Team Allison started her college career as a business major, but after one design course, she found her passion. She changed majors to Human Computer Interaction, and applied to our internship after learning about MongoDB in one of her data analytics classes. Much like Marcus and Tyler, she got to work on Stitch when it was still a new product. “I worked on creating a consumption dashboard for Stitch to show usage and make sure people didn’t get surprising bills,” she recalled. “It was great because I felt like I owned the project and I had my mentor to support me when I needed it.” She even got the final “LGTM” from our CTO, and felt like she was making a huge impact. Allison decided to come back to MongoDB as a Product Design New Grad on the Documentation team. Her biggest lesson? “You’re never too young to voice your thoughts and opinions,” she said. “My experience at MongoDB has been empowering for me to understand that my opinions and thoughts are unique and sets me apart from other people. People want to hear what you have to say.” Nataly Carbonell Intern Class: 2019 University: University of Florida Current Title & Team: Software Engineer, Atlas Nataly joined us as an intern during the summer of 2019. She interned on the Drivers team, and remembered that the internship really brought her out of her shell. “I consider myself introverted,” Nataly shared. “But it was very easy for me to get along with other interns. There was always something going on for us. I got to know MongoDB through the Speaker Series, which was an opportunity for leaders and executives to speak to the interns, and got to know the people through the events.” Nataly went through the New Grad rotation program, which she was grateful for to help her learn the type of work she wanted to do. “The culture throughout all the teams at MongoDB is very similar. Each team has different ways that they prefer to work and it was nice to see the various options. It was a good experience to see how teams interact and see differences in team sizes.” She now works on the Atlas team, and is enjoying the culture of the team immensely. “People on my team are always going out of their way to help one another.” Jenny Peshansky Intern Class: 2020 University: Stony Brook Current Title & Team: New Grad Software Engineer, Currently Rotating Jenny’s internship was like no one else’s on this list, as hers took place during the global COVID-19 pandemic! While she did interview in the office in the Fall of 2019, her internship took place remotely on the Server team. Despite the transition, Jenny had an incredible summer. “I didn’t expect to enjoy it as much as I did,” she admitted. “The internship program did a really good job adapting to the unprecedented situation and was the high point of my pandemic experience. The amount of social events was really great because I was super lonely, like we all were. I was able to get to know people and the program gave me purpose.” Jenny decided to join us as a New Grad and is currently going through her rotations on various engineering teams. When talking about her decision to come back she recalled, “I’ve had my mind set on MongoDB from the beginning. The internship only further reinforced that.” We are excited to see where Jenny ends up! The Future Why has MongoDB made such a big investment in our internships? After 10 years of iterating and improving, a third of our U.S. engineers come from our Campus Programs. On top of that, our interns and New Grads stay with MongoDB to grow their careers. A fifth of our Software Engineering leadership team were former interns and New Grads. “We’ve demonstrated the benefit of having a strong pipeline of young engineers,” Dan Pasette shared. However, it doesn’t come without hard work and dedication from the business. “We’ve had really great leadership in Campus Recruiting through the years. If we didn’t have the commitment to staff it properly, there’s no way we could have been successful. We were very intentional about having a system in place and iterating on that system every year to make improvements.” 10 years of continued success is an incredible accomplishment worth celebrating, but we aren’t done yet! Our program continues to grow to 4 continents and new business units, and we are so excited for what is to come. Interested in an internship at MongoDB? Keep an eye out for our student opportunities !
How Edenlab Built a High-Load, Low-Code FHIR Server to Deliver Healthcare for 40 Million Plus Patients
The Kodjin FHIR server has speed and scale in its DNA. Edenlab, the Ukrainian company behind Kodjin , built our original FHIR solution to digitize and service the entire Ukrainian national health system. The learnings and technologies from that project informed our development of the Kodjin FHIR server. At Edenlab, we have always been driven by our passion for building solutions that excel in speed and scale. With Kodjin, we have embraced a modern tech stack to deliver unparalleled performance that can handle the demands of large-scale healthcare systems, providing efficient data management and seamless interoperability. Eugene Yesakov, Solution Architect, Author of Kodjin Built for speed and scale While most healthcare projects involve handling large volumes of data, including patient records, medical images, and sensor data, the Kodjin FHIR server is based on a system developed to handle tens of millions of patient records and thousands of requests per second, to ensure timely access and efficient decision-making for a population of over 40 million people. And all of this information had to be processed and exchanged in real-time or near real-time, without delays or bottlenecks. This article will explore some of the architectural decisions the Edenlab team took when building Kodjin, specifically the role MongoDB played in enhancing performance and ensuring scalability. We will examine the benefits of leveraging MongoDB's scalability, flexibility, and robust querying capabilities, as well as its ability to handle the increasing velocity and volume of healthcare data without compromising performance. About Kodjin FHIR server Kodjin is an ONC-certified and HIPAA-compliant FHIR Server that offers hassle-free healthcare data management. It has been designed to meet the growing demands of healthcare projects, allowing for the efficient handling of increasing data volumes and concurrent requests. Its architecture, built on a horizontally scalable microservices approach, utilizes cutting-edge technologies such as the Rust programming language, MongoDB, ElasticSearch, Kafka, and Kubernetes. These technologies enable Kodjin to provide users with a low-code approach while harnessing the full potential of the FHIR specification. A deeper dive into the architecture approach - the role of MongoDB in Kodjin When deciding on the technology stack for the Kodjin FHIR Server, the Edenlab team knew that a document database would be required to serve as a transactional data store. In an FHIR Server, a transactional data store ensures that data operations occur in an atomic and consistent manner, allowing for the integrity and reliability of the data. Document databases are well-suited for this purpose as they provide a flexible schema and allow for storing complex data structures, such as those found in FHIR data. FHIR resources are represented in a hierarchical structure and can be quite intricate, with nested elements and relationships. Document databases, like MongoDB, excel at handling such complex and hierarchical data structures, making them an ideal choice for storing FHIR data. In addition to supporting document storage, the Edenlab team needed the chosen database to provide transactional capabilities for FHIR data operations. FHIR transactions, which encompass a set of related data operations that should either succeed or fail as a whole, are essential for maintaining data consistency and integrity. They can also be used to roll back changes if any part of the transaction fails. MongoDB provides support for multi-document transactions , enabling atomic operations across multiple documents within a single transaction. This aligns well with the transactional requirements of FHIR data and ensures data consistency in Kodjin. Implementation of GridFS as a storage for the terminologies in Terminology service Terminology service plays a vital role in FHIR projects, requiring a reliable and efficient storage solution for terminologies used. Kodjin employs GridFS , a file system within MongoDB designed for storing large files, which makes it ideal to handle terminologies. GridFS offers a convenient way to store and manage terminology files, ensuring easy accessibility and seamless integration within the FHIR ecosystem. By utilizing MongoDB's GridFS, Kodjin ensures efficient storage and retrieval of terminologies, enhancing the overall functionality of the terminology service. Kodjin FHIR server performance To evaluate the efficiency and responsiveness of the Kodjin FHIR server in various scenarios we conducted multiple performance tests using Locust, an open-source load testing tool. One of the performance metrics measured was the retrieval of resources by their unique ids using the GET by ID operation. Kodjin with MongoDB achieved a performance of 1721.8 requests per second (RPS) for this operation. This indicates that the server can efficiently retrieve specific resources, enabling quick access to desired data. The search operation, which involves querying ElasticSearch to obtain the ids of the searched resources and retrieving them from MongoDB, exhibited a performance of 1896.4 RPS. This highlights the effectiveness of polyglot persistence in Kodjin, leveraging ElasticSearch for fast and efficient search queries and MongoDB for resource retrieval. The system demonstrated its ability to process search queries and retrieve relevant results promptly. In terms of resource creation, Kodjin with MongoDB showed a performance of 1405.6 RPS for POST resource operations. This signifies that the system can effectively handle numerous resource-creation requests. The efficient processing and insertion of new resources into the MongoDB database ensure seamless data persistence and scalability. Overall, the performance tests confirm that Kodjin with MongoDB delivers efficient and responsive performance across various FHIR operations. The high RPS values obtained demonstrate the system's capability to handle significant workloads and provide timely access to resources through GET by ID, search, and POST operations. Conclusion Kodjin leverages a modern tech stack including Rust, Kafka, and Kubernetes to deliver the highest levels of performance. At the heart of Kodjin is MongoDB, which serves as a transactional data store. MongoDB's capabilities, such as multi-document transactions and flexible schema, ensure the integrity and consistency of FHIR data operations. The utilization of GridFS within MongoDB ensures efficient storage and retrieval of terminologies, optimizing the functionality of the Terminology service. To experience the power and potential of the Kodjin FHIR server firsthand, we invite you to contact the Edenlab team for a demo. For more information On MongoDB’s work in healthcare, and to understand why the world’s largest healthcare companies trust MongoDB, read our whitepaper on radical interoperability .