MongoDB 3.2.6 is out and is ready for production deployment. This release contains only fixes since 3.2.5, and is a recommended upgrade for all 3.2 users.
Fixed in this release:
- SERVER-22970 Background index contains mismatched index keys and documents
- SERVER-22043 count helper doesn’t apply read preference
- SERVER-23394 AuthorizationManager may deadlock while building role graph if profiling is enabled
- SERVER-23766 Remove beta startup warning for inMemory storage engine
As always, please let us know of any issues.
– The MongoDB Team
Back to Basics: Learn about MongoDB in Six Easy Steps
On May 5th we will launch a new Back to Basics webinar series . The goal of this series is to provide a gentle introduction to MongoDB for people who are new to NoSQL and are interested in accelerating their own knowledge of MongoDB. This six part series will take you from the basics of NoSQL to building and deploying your first MongoDB application. Participants are expected to have a technical background and should have at least a basic grasp of relational database technology. Some programming experience will definitely help you to get your head around the examples. The six webinars in the series are described below. Visit here to register for all the webinars in the series . Webinar 1: Introduction to NoSQL We start the series by taking a look at NoSQL and why you should care. We will cover the differences between the main types of NoSQL databases - document stores, wide column stores, and key value stores. Webinar 2: Your First MongoDB Application Next, we explore the details of how to build an application in MongoDB. We will cover the types of entities that we work with in a document database, as well as how to build document-based applications and how to manage performance, including the role of indexes. Webinar 3: Schema Design, Thinking in Documents In the third part of our series, we take a deeper look at the challenges of schema design. We will explore how to map relational schema into MongoDB, and how to optimize schema design for reads and writes. Finally, we’ll take a look at an interesting and unique feature of MongoDB - document validation. Webinar 4: Advanced Indexing, Text and Geospatial Indexes One of the key value propositions of MongoDB is its advanced library of indexing techniques. In this webinar we outline how to tune indexes. We then look at our text index capabilities which allow us to do free text searching within fields in the database, and our geospatial capabilities which allow you to search based on location. Webinar 5: Introduction to the Aggregation Framework The aggregation framework is one of the most powerful analytical tools available for MongoDB. In the fifth part of our series we explore how to create a pipeline of operations that can reshape and transform your data and apply a range of analytics functions and calculations to produce summary results across a data set. Webinar 6: Production Deployment In the final talk of the series we will explain how we create a stable production environment. You will learn how to create MongoDB production deployments that can survive many different failure scenarios. You will also learn how to create a scalable cluster than can handle any increase in the production workload. We will also introduce some of the production deployment tools that we can use to automate management and deployment. The whole series will be recorded and made available for review by all participants. If after attending these bite sized pieces of training you want to dig deeper we recommend you look at our extensive program of free training at MongoDB University . We look forward to seeing you online for the first episode on May 5th! Back to Basics Webinar 1: Introduction to NoSQL About the Author - Joe Drumgoole Joe is Director of Developer Advocacy EMEA at MongoDB. At MongoDB he helps developers to understand and utilise MongoDB in order to unleash the power of software and data for innovators everywhere. He is a software entrepreneur with over 25 years experience of successful product delivery at Digital Equipment Corporation, Nomura, Oracle Corporation, CR2 and Cape Clear Software. He has founded three software startups. Joe is a regular speaker at technical conferences and has provided mentoring and advice to many Startups over the past ten years.
4 Critical Features for a Modern Payments System
The business systems of many traditional banks rely on solutions that are decades old. These systems, which are built on outdated, inflexible relational databases, prevent traditional banks from competing with industry disruptors and those already adopting more modern approaches. Such outdated systems are ill-equipped to handle one of the core offerings that customers expect from banks today — instantaneous, cashless, digital payments . The relational database management systems (RDBMSes) at the core of these applications require breaking data structures into a complex web of tables. Originally, this tabular approach was necessary to minimize memory and storage footprints. But as hardware has become cheaper and more powerful, these advantages have also become less relevant. Instead, the complexity of this model results in data management and programmatic access issues. In this article, we’ll look at how a document database can simplify complexity and provide the scalability, performance, and other features required in modern business applications. Document model To stay competitive, many financial institutions will need to update their foundational data architecture and introduce a data platform that enables a flexible, real-time, and enriched customer experience. Without this, new apps and other services won’t be able to deliver significant value to the business. A document model eliminates the need for an intricate web of related tables. Adding new data to a document is relatively easy and quick since it can be done without the usually lengthy reorganization that RDBMSes require. What makes a document database different from a relational database? Intuitive data model simplifies and accelerates development work. Flexible schema allows modification of fields at any time, without disruptive migrations. Expressive query language and rich indexing enhance query flexibility. Universal JSON standard lets you structure data to meet application requirements. Distributed approach improves resiliency and enables global scalability. With a document database, there is no need for complicated multi-level joins for business objects, such as a bill or even a complex financial derivative, which often require object-relational mapping with complex stored procedures. Such stored procedures, which are written in custom languages, not only increase the cognitive load on developers but also are fiendishly hard to test. Missing automated tests present a major impediment to the adoption of agile software development methods. Required features Let’s look at four critical features that modern applications require for a successful overhaul of payment systems and how MongoDB can help address those needs. 1. Scalability Modern applications must operate at scales that were unthinkable just a few years ago, in relation to both transaction volume and to the number of development and test environments needed to support rapid development. Evolving consumer trends have also put higher demands on payment systems. Not only has the number of transactions increased, but the responsive experiences that customers expect have increased the query load, and data volumes are growing super-linear. The fully transactional RDBMS model is ill suited to support this level of performance and scale. Consequently, most organizations have created a plethora of caching layers, data warehouses, and aggregation and consolidation layers that create complexity, consume valuable developer time and cognitive load, and increase costs. To work efficiently, developers also need to be able to quickly create and tear down development and test environments, and this is only possible by leveraging the cloud. Traditional RDBMSes, however, are ill suited for cloud deployment. They are very sensitive to network latency, as business objects spread across multiple tables can only be retrieved through multiple sequential queries. MongoDB provides the scalability and performance that modern applications require. MongoDB’s developer data platform also ensures that the same data is available for use with other frequent consumption patterns like time series and full-text search . Thus, there is no need for custom replication code between the operational and analytical datastore. 2. Resiliency Many existing payment platforms were designed and architected when networking was expensive and slow. They depend on high-quality hardware with low redundancy for resilience. Not only is this approach very expensive, but the resiliency of a distributed system can never be reached through redundancy. At the core of MongoDB’s developer data platform is MongoDB Atlas , the most advanced cloud database service on the market. MongoDB Atlas can run in any cloud, or even across multiple clouds, and offers 99.995% uptime. This downtime is far less than typically expected to apply necessary security updates to a monolithic legacy database system. 3. Locality and global coverage Modern computing demands are at once ubiquitous and highly localized. Customers expect to be able to view their cash balances wherever they are, but client secrecy and data availability rules set strict guardrails on where data can be hosted and processed. The combination of geo-sharding, replication, and edge data addresses these problems. MongoDB Atlas in combination with MongoDB for Mobile brings these powerful tools to the developer. During the global pandemic, more consumers than ever have begun using their smartphones as payment terminals. To enable these rich functions, data must be held at the edge. Developing the synchronization of the data is difficult, however, and not a differentiator for financial institutions. MongoDB for Mobile, in addition with MongoDB’s geo-sharding capability on Atlas cloud, offloads this complexity from the developer. 4. Diverse workloads and workload isolation As more services and opportunities are developed, the demand to use the same data for multiple purposes is growing. Although legacy systems are well suited to support functions such as double entry accounting, when the same information has to be served up to a customer portal, the central credit engine, or an AI/ML algorithm, the limits of the relational databases become obvious. These limitations have resulted in developers following what is often called “best-of-breed” practices. Under this approach, data is replicated from the transactional core to a secondary, read-only datastore based on technology that is better suited to the particular workload. Typical examples are transactional data stores being copied nightly into data lakes to be available for AI/ML modelers. The additional hardware and licensing cost for this replication are not prohibitive, but the complexity of the replication, synchronization, and the complicated semantics introduced by batch dumps slows down development and increases both development and maintenance costs. Often, three or more different technologies are necessary to facilitate the usage patterns. With its developer data platform, MongoDB has integrated this replication, eliminating all the complexity for the developers. When a document is updated in the transactional datastore, MongoDB will automatically make it available for full-text search and time series analytics. The pace of change in the payments industry shows no signs of slowing. To stay competitive, it’s vital that you reassess your technology architecture. MongoDB Atlas is emerging as the technology of choice for many financial services firms that want to free their data, empower developers, and embrace disruption. Replacing legacy relational databases with a modern document database is a key step toward enhancing agility, controlling costs, better addressing consumer expectations, and achieving compliance with new regulations. Learn more by downloading our white paper “Modernize Your Payment Systems."