Top 5 MongoDB Podcast Episodes in 2022 (so far)
At MongoDB, one of our core values is to be focused on building together. One way we lean into this value is by bringing some of the best voices and stories from the database and tech communities onto our podcast. Podcasts help communities learn and connect. So as we head toward the end of the year, let’s take a look back—or, perhaps, a listen back—to our top episodes based on listens from The MongoDB Podcast so far in 2022. Episode 107 - Introduction to WiredTiger with Dr. Michael Cahill Dr. Michael Cahill co-founded the WiredTiger company and the storage engine by the same name. In our most-listened to episode from 2022 so far, Dr. Cahill sits down with Michael to talk about the storage engine, its strengths and capabilities, and a little about his journey as a database industry legend. Episode 108 - Exploring Postman with Arlemi Turpault In this episode of the MongoDB Podcast, Michael Lynn discusses Postman with Arlemi Turpault, Senior Developer Advocate at Postman. Postman is an application used for API testing. It is an HTTP client that tests HTTP requests, utilizing a graphical user interface through which we obtain different types of responses that need to be validated. Episode 109 - Prisma and MongoDB - Better Together Prisma is an open source ORM for Node.js and TypeScript that helps developers build faster and make fewer errors. On this episode, host Mike Lynn sits down with Nikolas Burk and Matt Miller of the Prisma team to discuss the Prisma + MongoDB launch week. Burk is a Developer Advocate and Miller is a Product Manager at Prisma, and together they outline what Prisma is now capable of with MongoDB support, including effects on developer workflows and efficiency. Episode 106 - Securing the Internet with Josh Aas, Sarah Gran of ISRG In this episode of the podcast, Michael talks with Josh Aas and Sarah Gran of the Internet Security Research Group (ISRG). They walk listeners through their mission to secure the internet through projects like Let's Encrypt , the automated digital certificate authority, and Prossimo , which focuses on transforming risks around memory safety in popular open source projects. MongoDB World Series Our number five blog so far in 2022 was a preview of MongoDB World. But why listen to a preview when you can dive into the actual event? Live at MongoDB World 2022, host Michael Lynn met with a variety of customers, partners, and experts on-site in New York City. Those conversations formed a great series filled with stories, learning and community. Check out the series episodes: Ep. 121 The MongoDB World Series - Oli Proulx from ChargeHub Ep. 120 The MongoDB World Series - Simcha Coleman from Inspirit Ep. 119 The MongoDB World Series - David Sarabia from inRecovery Ep. 118 The MongoDB World Series - Nick Gamble from Unqork Ep. 117 The MongoDB World Series - Beray Bentesen from Qubitro Ep. 116 The MongoDB World Series - Vatsal Singhal from Ultrahuman Subscribe to The MongoDB Podcast wherever you listen to your podcasts so you can stay up to date with all our new episodes, dropping weekly. And if you are a tech expert or enthusiast with a passion for sharing your thoughts, opinions, and stories, connect with Michael Lynn to discuss a podcast guest opportunity.
How to Leverage Enriched Queries with MongoDB 6.0
MongoDB introduces useful new functions and features with every release, and MongoDB 6.0, released this summer, offers many notable improvements , including deeper insights from enriched queries via the MongoDB Query API . This set of query enhancements was announced at MongoDB World 2022 by senior product manager Katya Kamenieva. You can watch her presentation below. Watch Kayta Kamenieva’s MongoDB World presentation on queries. Users can now use upgraded operators and change stream features. In this post, we’ll look at several of these updates, along with examples of how you can put them to use. Top N accumulators With this new feature, users can compute top items in each group based on the sort criteria ( $topN , $bottomN ), current order of documents ($firstN, $lastN), or value of a field ( $manX , $minN ). This functionality would be useful, for example, if you have a collection of restaurants with ratings, and you want to see the top three highest-rated restaurants based on the type of cuisine. You can group by cuisine and use $topN to return the top three restaurants by rating. Ability to sort arrays The ability to sort an array allows users to sort elements in the array. For example, suppose you have posted content with hundreds of user comments, and you want to sort the comments based on how many likes they received. In this case, $sortArray can pull those comments and prioritize them to the top of the comments list. Densification and gap-filling These new additions to the aggregation framework help to build out time series data more completely. When attempting to create histograms of data over time, the new stages, $denisfy and $fill , allow you to fill gaps in that data to create smoother and more complete graphs using linear interpolation, last/next observed value carried forward, or a constant value. This capability can be helpful, for example, if you want to create a graph that shows the amount of inventory in a warehouse every day for a year, but the inventory was only recorded once a week. The $densify expression will fill the gaps in the timeline, while $fill will produce values for the inventory data based on the previous observation. Joining sharded collections With this new feature, when joining collections using $lookup or performing recursive search with $graphLookup , collections on both sides can be sharded. Before 6.0, only the originating collection could be sharded. An example use case is enriching records in the “accounts” collection with the list of the corresponding orders that are stored in the “orders” collection. In the past, only “accounts” collections could be sharded. Starting with 6.0, both “accounts” and “orders” collections can be sharded. Change streams pre- and post-images Change streams now offer point-in-time (PIT) pre- and post-image capabilities , allowing users to include the state of the document before and after changes in the output of the change stream. This functionality can be useful in many situations. For example, suppose a company is tracking flight times. If a flight is delayed, the system can compare the value of the departure and arrival times both before and after that delay and trigger an automatic rewrite of the schedule for the new flight timeline, including schedules for the entire crew. Atlas Search across multiple collections This improvement to MongoDB Atlas Search allows users to search across multiple collections with a single query using $search inside the $unionWith or $lookup stages. $search can provide these results quickly, using only one query. Enriched queries are not the only improvements in MongoDB 6.0. Read about the 7 reasons to upgrade to MongoDB 6.0 and discover the possibilities. Try MongoDB Atlas for Free Today
Moving From Monolith to Microservices: Mark Porter and Accenture’s Michael Ljung Explain
The first step in digital transformation for many organizations is to migrate from legacy on-premises environments and move as many workloads as possible into the public cloud. As seen in the first in our series of conversations between Mark Porter, CTO of MongoDB, and Michael Ljung, Accenture ’s Global Lead, Software Engineering, Accenture Cloud First, this is not always easy, but with the right tools and planning, that migration can reap great benefits. The next step in many organizations’ transformation is to dismantle their monolithic applications — which often limit businesses’ ability to quickly innovate — and move to applications built on a microservices architecture. Many organizations are already well on their way. Research shows that 36% of large companies, 50% of medium companies, and 44% of small companies are already using microservices in their production and development. To explain this migration away from the monolith, Porter and Ljung sat down to discuss the benefits of microservices, how to size those services properly for best results, and how an Accenture customer used a microservices approach to quickly roll out new features to help provide COVID-19 vaccinations. Watch their full discussion: Why microservices? Although teams choose a microservice architecture for a variety of reasons and use cases , one driving force is that businesses now rely so heavily on software for competitive advantage that they require a more rapid development cycle for new releases. A monolithic approach does not support the fast time-to-market cycles needed, nor does it provide the working environment developers need to speed the release process. In their conversation, Porter and Ljung cover several benefits of moving away from the monolith and adopting microservices at the proper size, including the following: Microservices align to how humans work best together. A large, monolithic codebase leads to complexity and creates immense cognitive loads for the developers. They offer protection from complete downtime. Microservices allow for compartmentalization to avoid a single point of failure. By contrast, with a monolithic application, if something goes wrong, everything goes wrong. They allow for better application scaling. With a microservices architecture, only the features that require extra performance need to be scaled. And they allow you to increase your speed to market. Some teams have reported that moving to microservices and containers saw a 13x increase in the frequency of software releases . Read the first installment in this cloud migration series, “ Migrating to the Cloud Isn't As Easy As Most People Think .”
Migrating to the Cloud Isn't As Easy As Most People Think: A Conversation With Mark Porter and Accenture’s Michael Ljung
Moving away from a legacy relational database and developing a strategy around your cloud journey can unlock value that is otherwise limited without a streamlined, simplified, and modernized cloud architecture. But that outcome is by no means guaranteed. Although the journey to the cloud is often painted as an easy path to simplicity, agility, and scalability, the quickest way to migrate, the lift-and-shift approach , can encourage organizations to arrive to the public cloud and begin deploying new software and resources without considering the complexity they can create — and without having solved for architectural considerations prior to migration. Think about packing for a big move. It’s a best practice to purge unnecessary items, clean, and organize, so you arrive at your new home with a better understanding of what you need, what you own, and how useful those items will be in your new place. Likewise, considerations around applications and database architectures are best addressed prior to migration. Without a proper migration strategy in place, businesses arrive in the cloud with the same complex architecture, an excessive amount of siloed data, and the weight of unnecessary applications. It’s the same organization with the same operations, only located in a new landscape. If your business is currently frustrated by the course corrections needed after a migration, partners like Accenture and MongoDB can help organize your cloud environment and your database architecture. MongoDB CTO Mark Porter recently sat down with Michael Ljung , Accenture’s global engineering lead, to discuss the benefits of cloud migration — and to get real about the challenges. According to Ljung, there are real and immediate benefits to migrating. For example, a study by Accenture found that customers were seeing a 10% cost savings stemming from migrating applications in a lift-and-shift fashion. But that number is small compared to the potential benefits of the cloud. Ljung says that it’s also important to replace the mindset of simple migration as the ultimate goal and to focus more on modernization, co-creating, innovating, and differentiating. This means thinking of the cloud in a new way. Migration is the start of a journey, not the final destination. It means refactoring, repurposing, replacing, or retiring applications altogether when necessary. This mentality also applies to database architectures in the cloud; many companies believe they can move their relational database to the cloud and database operations will automatically improve in terms of productivity. This is not realistic, and not the mindset for driving the best database strategy. Accenture helps client organizations assess their current cloud state and implement their MAGI methodology —that is, to modernize, accelerate, grow, and innovate. Learn more about modernizing your apps with MongoDB before beginning a cloud migration.
4 New MongoDB Features to Improve Security and Operations
Data platforms are designed to remove operational complexity and enable developers to move and innovate faster. For applications that are critical to your users and your business, the data platform powering them must also be reliable, scalable, and global. Achieving that should take minimal work, both upfront and on an ongoing basis. At MongoDB World 2022, we announced several new capabilities that further help organizations achieve operational excellence: Queryable Encryption , Cluster-to-Cluster Sync , Scheduled Archiving , MongoDB Atlas Operator for Kubernetes , and MongoDB Atlas Serverless . With the introduction of Queryable Encryption , MongoDB will be the only database provider that allows customers to run expressive queries such as equality and range, prefix, suffix, substring and more on fully randomly encrypted data, just as they can do on unencrypted data. This is a huge advantage for organizations that need to run expressive queries while also securing their data. Queryable Encryption reduces the heavy lifting involved when working with encrypted data, resulting in faster app development without undermining data protection or compliance with data privacy regulations. Not every organization is fully — or may ever be fully — in the cloud. Many businesses also leverage hybrid or multi-cloud environments. Cluster-to-Cluster Sync enables continuous, uni-directional, real-time data synchronization of two MongoDB clusters in the same or different environments — public cloud, private cloud, on-premises, and at the edge. MongoDB now supports, for example, hybrid Atlas and Enterprise Advanced deployments, wherein a cluster’s data can be synced from on-prem to Atlas, or vice versa. With Cluster-to-Cluster Sync, organizations have full control of the synchronization process. They can decide when to start, stop, pause, or resume your synchronization, or to reverse the direction of synchronization. And they can monitor the progress of the synchronization in real time. This new capability will enable greater experimentation and innovation, increase organizational insights, and help developers find more efficient ways to work with data. Use cases that benefit from having the data of two MongoDB clusters fully synchronized include data migration, enhanced development lifecycles, dedicated analytics, audit compliance, and improving latency by moving data to the edge. The MongoDB Atlas Operator for Kubernetes is the best way to use MongoDB with Kubernetes. With the Atlas Operator, developers can seamlessly integrate MongoDB Atlas into their Kubernetes deployment pipeline, controlling Atlas resources without leaving the Kubernetes control plane. They can also control Atlas projects, clusters, database users, backup policy, serverless instances, private network endpoints, and more. The operator is compatible with any certified Kubernetes distribution, including Amazon Elastic Kubernetes Service (EKS), Google Kubernetes Engine (GKE), Azure Kubernetes Service (AKS), Red Hat OpenShift, and dozens more. We are enhancing the Online Archive feature of Atlas with two new features: Data expiration and scheduled archiving. With data expiration, you can define and automate for how long you need the data stored in the online archive before getting deleted. With the scheduled archiving feature, you can set rules about the time window of when you want the archive to run. This could be daily, weekly or monthly. You can also edit the archive rule and define when you want to archive your data and when you want it deleted from the archive. One big trend in the developer world is removing operational overhead by moving to a managed database offering. This move away from day-to-day management and administration lets developers do what they do best — create. To this end, MongoDB has rolled out Atlas Serverless . With Atlas Serverless, server provisioning and management has been abstracted (hidden) from the customer or end-user of the service. This eliminates the cognitive load of sizing and scaling infrastructure to keep up with application demand. Instead of paying for idle resources, with Atlas Serverless, you pay for only what you use. By simplifying provisioning, Atlas Serverless helps organizations accelerate time to market and improve experiences for both developers and IT managers. All of these new features have been designed to help organizations improve their operational excellence, ensuring security, consistency, and scale while alleviating repetitive operational tasks for developers and IT managers. Learn more about MongoDB World 2022 announcements at mongodb.com/new and in these stories: 5 New Analytics Features to Accelerate Insights and Automate Decision-Making Closing the Developer Experience Gap: MongoDB World Announcements Streamline, Simplify, Accelerate: New MongoDB Features Reduce Complexity
Every Day Is Tax Day When Your Data Architecture Is Too Complex
Mid-April marks the deadline for filing income taxes in the United States. It’s a moment when the reality of your earnings for the year are made clear and you can see where your money comes from — and where it’s going. Our personal lives are not the only realm where taxation occurs. At MongoDB, we have seen how organizations with overly complex data architectures — whether a legacy system or a sprawl of cloud-native components, or a hybrid with messes on both sides — are paying a price: a tax on innovation. DIRT: The data and innovation recurring tax The data and innovation recurring tax, or DIRT, is fundamentally rooted in data, because huge amounts of data must be generated to support legacy database technologies. Modern applications use features such as real-time data to create rich user experiences, so developers must cobble together niche databases with cumbersome pipelines to move data between them. Or, organizations move some of their applications and data to the cloud, grabbing a bunch of off-the-shelf software that doesn’t work or play well together. The time developers spend creating workarounds? That’s a tax on innovation. Instead of working on new features that the business needs and customers will love, teams are stuck supporting complex, brittle architectures. And this is not a one-and-done tax. DIRT applies to every new project, making each one a little more difficult to manage and maintain as new components, frameworks, and protocols are added. Read more about the innovation tax in our white paper DIRT and the High Cost of Complexity . Complexity is the enemy of innovation When you pay income tax, you have some idea about how that money will be spent. Taxes support initiatives. But what does DIRT support? Nothing, except a spaghetti architecture that isn’t a sustainable foundation for your organization’s future. If your database is experiencing the symptoms of complexity now, what will the experience be like in one, five, or a dozen years? Complexity is a drain, plain and simple. The good news is, reducing complexity can turn that drain into a fountain. Removing DIRT improves the developer experience and hastens your time to market. It also leaves you with more opportunities to innovate — and more money to support those innovations. Complexity costs money — but how can you tell if your database is too complex? Our guide 10 Signs Your Data Architecture Is Holding You Back details the ways a creaky data architecture is taxing your team. We know that innovation is what separates the businesses of today from the businesses of tomorrow. Every day you are not innovating, some other organization is. This Tax Day, don’t let your legacy database and the price tag that comes with it hold you back.