March 15, 2022
Over the past few weeks, the situation in Ukraine has escalated into a full-fledged war and humanitarian crisis. We continue to monitor the situation and its impact across the world. At this time, MongoDB does not have any offices or employees based in Russia. We have had limited business operations in Russia.
The breadth of the new sanctions from the US and internationally is unprecedented, and MongoDB has taken action to comply with them. We will not sell our cloud services to customers in Russia and Belarus and we will not sell any more MongoDB software to customers in Russia or Belarus.
For those in Ukraine, MongoDB is trying to do our part to help in a number of ways. MongoDB employees have donated directly to organizations that are helping people in crisis in the region. MongoDB, as an organization, has offered free Atlas credits to a project called Unterkunft Ukraine, which helps refugees fleeing Ukraine find temporary housing.
We are also making free MongoDB Atlas credits available for organizations that are developing software projects to help alleviate the current humanitarian crisis in Ukraine. If you are working on a project that provides assistance in the region, fill out the application to apply for free MongoDB Atlas credits.
MongoDB and AWS Expand Global Collaboration
MongoDB launched as a developer-friendly, open source database in 2009, but it wasn't until 2016, when we released MongoDB Atlas , our fully managed database service, that the full vision for MongoDB truly emerged. Realizing that vision, however, has never been a solo effort. From the earliest days, MongoDB has partnered with a range of companies, but none more closely than with Amazon Web Services (AWS) as we've joined forces to make the developer experience as seamless as possible. Now we're kicking that partnership into overdrive. As announced today , MongoDB is expanding our global partnership with AWS. Though details of the agreement are confidential, the results will not be: Customers stand to benefit from deeper, broader technical integrations, improvements in migrating workloads from legacy data infrastructure to modern MongoDB Atlas, and more. For those of us who have worked to grow this partnership, it's exciting (and rewarding!) to see the scope of the work envisioned by MongoDB and AWS, together. On that note, it's worth revisiting how we got here. Building together From the earliest days , we've positioned MongoDB as the best way to manage a wide variety of data types and sources, in real time, at significant scale. Back then we called it "Big Data," but now we recognize it for what it is: what all modern data looks like. Then and now, MongoDB came with an open license that encouraged developers to easily access and tune the database to their needs. And so they did, with many developers opting to run their instances of MongoDB on AWS, removing the need to buy and provision servers. In fact, almost from the start of the company, we have worked closely with AWS to ensure that MongoDB users and customers would have an excellent experience running MongoDB on AWS. It was a great start, but it wasn't enough. Developers, after all, still had to fiddle with the dials and knobs of managing the database. This began to change in 2011, when the company released the MongoDB Monitoring Service (MMS). MMS made it much easier to monitor MongoDB clusters of any size. By 2013, we rolled MMS, Backup, and other MongoDB services into the MongoDB Management Service, and continued to work closely with AWS to optimize these services for MongoDB customers. Then in 2016, again with extensive AWS assistance, we launched MongoDB Atlas, a fully managed, integrated suite of cloud database and data services to accelerate and simplify how developers build with data. Making life easier for developers was the vision that co-founders Dwight Merriman and Eliot Horowitz had when they started MongoDB (then 10gen) in 2007. That vision has always depended on a strong partnership with AWS. This partnership got even stronger, as we just announced , with the promise of even better serverless options, expanded use of AWS Graviton instances to improve performance at lower cost, and improved hybrid options through AWS Outposts. Beyond product, we'll also be more closely collaborating to reach and educate customers through joint Developer Relations initiatives, programs to reach new customers, and more. As good as our partnership has been, it just got significantly better. Although focusing on how the two companies compete may be convenient (for example, both organizations provide database services), how we cooperate is a more compelling story. So let's talk about that. A mutual obsession Over the past 15 years, MongoDB has built an extensive partner ecosystem around our application data platform. From open source mainstays like Confluent, to application development innovators like Vercel, data intelligence pioneers like BigID, and trusted system integration powerhouses like Accenture, we work closely with the best partners to ensure developers enjoy an exceptional experience working with MongoDB. As already noted, AWS is the partner with which we've worked most closely for the longest time. That partnership has resulted in tight integration between MongoDB and AWS services such as AWS Wavelength, Amazon Kinesis Data Firehose, Amazon EventBridge, AWS PrivateLink, AWS App Runner, Amazon Managed Grafana, and more. We also recently announced Pay as You Go Atlas on AWS Marketplace , giving customers even more options for how they run MongoDB on AWS. Additionally, as part of our new strategic agreement, we'll be offering joint customer incentive programs to make it even easier for customers to run proofs of concept and migrate from expensive legacy data infrastructure to MongoDB Atlas running on AWS. If this seems to paint an overly rosy picture of our partnership with AWS, it's worth remembering that the guiding principle for both AWS and MongoDB is customer obsession. Of course we've had moments when we've disagreed over how best to take care of customers, because every partnership has its fair share of friction. But behind the scenes, our product, marketing, and sales teams have worked together for years to meet customer needs. Customers seem to recognize this. In MongoDB's most recent earnings call, we announced that we now have more than 33,000 customers — including Shutterfly , Cox Automotive , Pitney Bowes , and Nesto Software — many of which choose to run Atlas on AWS. Still not convinced? There's perhaps no better way to understand what MongoDB can do for your organization than to try it. You can try Atlas for free , or you can choose to pay-as-you-go by starting with Atlas on the AWS Marketplace . Either way, we hope you'll let us know what you think.
Connected Healthcare Data: Interoperability to Solve Fragmentation and Drive Better Patient Outcomes
Many differences exist across healthcare systems around the globe, but there is one unfortunate similarity: fragmentation. Fragmentation is a consequence of the inability of various healthcare organizations (both public and private) to communicate with each other or to do so in a timely or consistent manner, and it can have a dramatic impact on patient and population well-being. Interoperability and communication A patient can visit a specialist for a specific condition and the family doctor for regular checkups, perhaps even on the same day. But how can both doctors make appropriate decisions if patient data is not shared between them? Fragmented healthcare delivery, as described in this scenario, also leads to data fragmentation. Such data fragmentation can cause misdiagnosis and services duplication. It can also lead to billing issues, fraud, and more, causing preventable harm and representing a massive economic burden for healthcare systems worldwide. To improve healthcare fragmentation, we need truly interoperable health data. The longitudinal patient record A longitudinal patient record (LPR) is a full, life-long view of a patient’s healthcare history and the care they’ve received. It’s an electronic snapshot of every interaction patients have, regardless of provider and service. Ideally, this record can be shared across any or all entities within a country’s healthcare system. The LPR represents a step beyond the electronic health record, extending past a specific healthcare network to a regional or national level. It’s critical that LPRs use the same data format and structure to guarantee the ability of healthcare providers to easily and quickly interact with them. Data standards for LPRs are key to interoperability and can help address healthcare fragmentation, which, in turn, can help save lives by improving care. FHIR Fast Healthcare Interoperability Resources (FHIR) is a commonly used schema that comprises a set of API and data standards for exchanging healthcare data. FHIR enables semantic interoperability to allow effective communication between independent healthcare institutions and essentially defines “how healthcare information can be exchanged between different computer systems regardless of how it is stored in those systems” ( ONC Fact Sheet, “What is FHIR?” ). FHIR aims to solve the fragmentation problem of the healthcare system by directly attacking the root of the problem: miscommunication. As is the case for many other modern communication standards (for example, ISO 20022 for finance ), FHIR builds its REST API from a JSON schema. This foundation is convenient, considering most modern applications are built with object-oriented programming languages that have JSON as the standard file and data interchange format. This approach also makes it easier for developers to build applications, which is perhaps the most important point: The future of healthcare delivery may increasingly depend on the creation of applications that will transform how patients and providers interact with healthcare systems for the better. MongoDB: FHIR and healthcare app-ification MongoDB is a document database and is therefore a natural fit for building FHIR applications. With JSON as the foundation of the MongoDB document model developers can easily store and retrieve data from their FHIR APIs to and from the database, with no translation or change of format needed. In fact, organizations can adopt FHIR resources as the basis of a new, canonical data model that existing internal systems can begin to shift and conform to. One example is the Exafluence FHIR API , which is built on top of MongoDB. Exafluence's API allows for real-time data interchange by leveraging Apache Kafka and Spark, in either an on-premise or multi-cloud deployment. Software teams leveraging the Exafluence solution have experienced velocity increases of their FHIR interoperability projects by 40% to 60% . MongoDB's tool set can develop value-add business solutions on the FHIR-native dataset — without ETL. Beyond FHIR , the trend toward healthcare app-ification (i.e., the increasing use of applications in healthcare) clashes with pervasive legacy architectures, which typically are not optimized for the developer experience. Because of this reliance on legacy architectures, modernization or transformation initiatives often fail to take hold or are postponed as companies perceive the risks to be too high and the return on investment is not evident. It doesn’t have to be this way, however. MongoDB’s industry-proven iterative approach to modernization reduces the risk of application and infrastructure migration and unlocks developer productivity and innovation. Interoperable, modern healthcare applications can now be built in a developer-friendly environment, with all the benefits expected from traditional databases (i.e., ACID transactions, expressive query language, and enterprise-grade security). MongoDB provides the freedom for solutions to be deployed anywhere (e.g., on-premises, multi-cloud), providing a major advantage for healthcare organizations, which typically have multi-environment deployments. Healthcare and the cloud Digital healthcare will accelerate the adoption of cloud technologies within the industry, enabling innovation at scale and unlocking billions of dollars in value. Healthcare organizations, however, have so far been reluctant to move workloads to the cloud, mostly because of data privacy and security concerns. To support such cloud adoption initiatives, MongoDB Atlas offers a unique multi-cloud data platform , integrating MongoDB in a fully managed environment with enterprise-grade security measures and data encryption capabilities. MongoDB Atlas is HIPPA-ready and a key facilitator for GDPR compliance. A holistic view of patient care Interoperable healthcare records and communication standards will make longitudinal patient records possible by providing a much-sought-after holistic view of the patient, helping to fix healthcare fragmentation. Many challenges still exist, including transforming legacy infrastructures into modern, flexible data platforms that can adapt to the exponential changes happening in the healthcare industry. MongoDB provides a developer data platform designed to unlock developer productivity and ultimately giving healthcare organizations the power to focus on what matters most: the patient. Learn more about how MongoDB supports healthcare organizations .