MongoDB 3.2.7-rc1 is released
MongoDB 3.2.7-rc1 is out and is ready for testing. This is a release candidate containing only fixes since 3.2.6. The next stable release 3.2.7 will be a recommended upgrade for all 3.2 users.
Fixed in this release:
- SERVER-18783: Upgrade MongoDB past PCRE 8.37
- SERVER-23919 Database/Collection drop during initial sync can cause collmod to fail initial sync
- SERVER-24054 JS segmentation fault on load of certain nans
- SERVER-24058 Connection pool asio doesn't honor setup timeouts
- SERVER-24062 Native CA certificates don't work with homebrew's openssl
- SERVER-24117 Mongo binaries ELF stack has become executable
- TOOLS-1166 Mongotop cannot connect to secondary in 3.2
- WT-2560 Stuck trying to update oldest transaction ID
As always, please let us know of any issues.
-- The MongoDB Team
Leaf in the Wild: Swisscom Builds its New Application Cloud PaaS for Microservices with Cloud Foundry, Docker, and MongoDB Enterprise Advanced
Leaf in the Wild posts highlight real world MongoDB deployments. Read other stories about how companies are using MongoDB for their mission-critical projects. Swisscom is leading the transformation from traditional telecommunications company to cloud services provider. Through its new Application Cloud, Swisscom is enabling independent developers through to multinational Swiss-based enterprises to build a new generation of cloud-native microservices on a highly scalable and secure Platform-as-a-Service (PaaS). I met with Marco Hochstrasser, Head of Cloud Platform Development at Swisscom, to learn more. Can you start by telling us a little bit about your company? Swisscom is the largest communications provider in Switzerland, delivering voice, mobile, broadband and TV services to 80% of the population. We generate annual revenues of €11bn, and employ over 20,000 people. A growing percentage of the company’s revenue comes from our enterprise business, providing companies in Switzerland with network, IT outsourcing, mobility, digital enterprise solutions and smart working. Cloud services are one of the fastest growing segments of the enterprise business. We provide the full range of infrastructure, software, and Platform-as-a-Service (PaaS) offerings for our enterprise customers in Switzerland. Can you tell us how you are using MongoDB? MongoDB is one of the core database offerings available through our PaaS services: The Swisscom Application Cloud is a public PaaS, available to any developer. The platform allows developers to concentrate on coding, leaving management of the underlying operating systems, middleware, and databases to us. The service was launched in October 2015 and already hosts thousands of cloud-native applications in modern container technology. The Swisscom Application Cloud Virtual Private is a newly launched offering that provides a dedicated PaaS for enterprise customers. It is hosted and managed in our Swiss data centers with interconnectivity directly to the customer’s own network and IT infrastructure. Whether using the public or virtual private Application Cloud, all data is stored in Switzerland on our own network and routed via our local, state-of-the-art data centres. This enables us to guarantee maximum security and smooth operation for local developers and enterprises. Why did you choose MongoDB as a service in the App Cloud? We offer traditional relational databases, along with caches, message queues and search engines. We wanted to include a non-relational option, and sought feedback from the market. MongoDB was the overwhelming choice – compared to Cassandra and Couchbase there is a significantly larger community around the product. There is much higher customer demand for MongoDB, especially from the verticals that constitute the main part of our customer base. Please describe the technology stack powering your public and private Application Cloud We are running an open-standards based stack across our PaaS offering, which enables our customers to avoid the lock-in inherent with other cloud services. The technology includes: ODM-built state of the art x86 hardware to scale efficiently Plumgrid software-defined networking to interconnect with Swisscom’s existing networks ScaleIO software-defined storage to bring policy-based provisioning and management to every layer of our technology stack Red Hat OpenStack with KVM virtualization for the IaaS layer Docker for running cloud-native containers (in Cloud Foundry), as well as persistent containers for stateful services Flocker to bring persistency into our service-container framework Cloud Foundry is our PaaS layer, providing a highly standardized and widely adopted platform. Swisscom is a gold member of the Cloud Foundation and I am a member of the board. Cloud Foundry and Docker do not currently provide persistence for stateful services, and so for databases such as MongoDB, we use Flocker from ClusterHQ to mount block storage from our software-defined storage to the container and persist its state. If the container terminates for whatever reason, Flocker transparently remounts the storage volume to the replacement container, with almost no interruption to the service or impact to the user experience. You can learn more about how we use Docker and Flocker to build a stateful database-as-a-service from our recent talk at the Tectonic Summit . Our technology stack gives us an agile devops environment, with continuous integration and delivery to push new features and upgrades rapidly into production. App Cloud is powering tens of thousands of microservices, managed by a small group of administrators. The key is that we heavily standardize, automate and monitor everything, and MongoDB integrates perfectly to the environment. How do you provision and manage MongoDB within the App Cloud? When a developer creates a service via the App Cloud UI or the API, the request goes to Cloud Foundry which calls its service broker to instantiate the MongoDB Docker container. The MongoDB Ops Manager RESTful API integrates with the Cloud Foundry service broker to provision the image, and Flocker mounts the block storage to the container. Deploying new MongoDB Services with Cloud Foundry Do you use any support and services for MongoDB? Yes, we are customers of MongoDB Enterprise Advanced which provides Ops Manager, and 24x7 proactive support direct from the MongoDB technical services and development teams. This enables us to provide a better SLA to our Application Cloud customers. We have also used the Health Check from MongoDB Global Consulting Services, which delivered a detailed readiness assessment of our deployment, with best practices for always-on availability, system configuration and scaling. How is MongoDB performing in the App Cloud? We’ve had great traction since the initial launch of the public Application Cloud. We have ramped to over 2,000 database containers in just a few months – more than half of which are running MongoDB. dorma+kaba Group , one of the world’s leading providers of physical security and access solutions, has developed its new Internet-based services for small and medium enterprises on the Application Cloud with MongoDB, and is able to continuously deliver updates as they release new features. Application Cloud Virtual Private has just been released, and we already have great feedback from the market, especially as we’re offering the service hosted in Switzerland, in local Swiss data centres. One of the key reasons for the interest we are seeing in MongoDB is that we are currently the only public cloud provider offering MongoDB Enterprise Advanced-as-a-Service in Switzerland, Germany and Austria, through our partnership with MongoDB. Customers get access to the value-added features of MongoDB Enterprise, including advanced security protection with encryption, auditing and centralized authentication; coupled with the fine grained monitoring and consistent, point in time backups available with Ops Manager. The service is based on the latest MongoDB 3.2 release . Does Swisscom use MongoDB outside of the App Cloud? We use it extensively for Over The Top (OTT) communications services in our residential division. The Swisscom IPTV platform runs MongoDB to manage the electronic program guide, Video on-Demand and radio channels for nearly 1 million subscribers Our latest project is the new Swisscom myCloud service providing secure multimedia content storage and management for over 8 million prospective customers. Marco, thank you for taking the time to share details of your App Cloud with me. Want to learn more about enabling microservices with containers and MongoDB? Read our new white paper. Enabling Microservices: Containers & Orchestration Explained About the Author - Mat Keep Mat is a director within the MongoDB product marketing team, responsible for building the vision, positioning and content for MongoDB’s products and services, including the analysis of market trends and customer requirements. Prior to MongoDB, Mat was director of product management at Oracle Corp. with responsibility for the MySQL database in web, telecoms, cloud and big data workloads. This followed a series of sales, business development and analyst / programmer positions with both technology vendors and end-user companies.
Accelerating to T+1 - Have You Got the Speed and Agility Required to Meet the Deadline?
On May 28, 2024, the Securities and Exchange Commission (SEC) will implement a move to a T+1 settlement for standard securities trades , shortening the settlement period from 2 business days after the trade date to one business day. The change aims to address market volatility and reduce credit and settlement risk. The shortened T+1 settlement cycle can potentially decrease market risks, but most firms' current back-office operations cannot handle this change. This is due to several challenges with existing systems, including: Manual processes will be under pressure due to the shortened settlement cycle Batch data processing will not be feasible To prepare for T+1, firms should take urgent action to address these challenges: Automate manual processes to streamline them and improve operational efficiency Event-based real-time processing should replace batch processing for faster settlement In this blog, we will explore how MongoDB can be leveraged to accelerate manual process automation and replace batch processes to enable faster settlement. What is a T+1 and T+2 settlement? T+1 settlement refers to the practice of settling transactions executed before 4:30pm on the following trading day. For example, if a transaction is executed on Monday before 4:30 pm, the settlement will occur on Tuesday. This settlement process involves the transfer of securities and/or funds from the seller's account to the buyer's account. This contrasts with the T+2 settlement, where trades are settled two trading days after the trade date. According to SEC Chair Gary Gensler , “T+1 is designed to benefit investors and reduce the credit, market, and liquidity risks in securities transactions faced by market participants.” Overcoming T+1 transition challenges with MongoDB: Two unique solutions 1. The multi-cloud developer data platform accelerates manual process automation Legacy settlement systems may involve manual intervention for various tasks, including manual matching of trades, manual input of settlement instructions, allocation emails to brokers, reconciliation of trade and settlement details, and manual processing of paper-based documents. These manual processes can be time-consuming and prone to errors. MongoDB (Figure 1 below) can help accelerate developer productivity in several ways: Easy to use: MongoDB is designed to be easy to use, which can reduce the learning curve for developers who are new to the database. Flexible data model: Allows developers to store data in a way that makes sense for their application. This can help accelerate development by reducing the need for complex data transformations or ORM mapping. Scalability: MongoDB is highly scalable , which means it can handle large volumes of trade data and support high levels of concurrency. Rich query language: Allows developers to perform complex queries without writing much code. MongoDB's Apache Lucene-based search can also help screen large volumes of data against sanctions and watch lists in real-time. Figure 1: MongoDB's developer data platform Discover the developer productivity calculator . Developers spend 42% of their work week on maintenance and technical debt. How much does this cost your organization? Calculate how much you can save by working with MongoDB. 2. An operational trade store to replace slow batch processing Back-office technology teams face numerous challenges when consolidating transaction data due to the complexity of legacy batch ETL and integration jobs. Legacy databases have long been the industry standard but are not optimal for post-trade management due to limitations such as rigid schema, difficulty in horizontal scaling, and slow performance. For T+1 settlement, it is crucial to have real-time availability of consolidated positions across assets, geographies, and business lines. It is important to note that the end of the batch cycle will not meet this requirement. As a solution, MongoDB customers use an operational trade data store (ODS) to overcome these challenges for real-time data sharing. By using an ODS, financial firms can improve their operational efficiency by consolidating transaction data in real-time. This allows them to streamline their back-office operations, reduce the complexity of ETL and integration processes, and avoid the limitations of relational databases. As a result, firms can make faster, more informed decisions and gain a competitive edge in the market. Using MongoDB (Figure 2 below), trade desk data is copied into an ODS in real-time through change data capture (CDC), creating a centralized trade store that acts as a live source for downstream trade settlement and compliance systems. This enables faster settlement times, improves data quality and accuracy, and supports full transactionality. As the ODS evolves, it becomes a "system of record/golden source" for many back office and middle office applications, and powers AI/ML-based real-time fraud prevention applications and settlement risk failure systems. Figure 2: Centralized Trade Data Store (ODS) Managing trade settlement risk failure is critical in driving efficiency across the entire securities market ecosystem. Luckily, MongoDB integration capabilities (Figure 3 below) with modern AI and ML platforms enable banks to develop AI/ML models that make managing potential trade settlement fails much more efficient from a cost, time, and quality perspective. Additionally, predictive analytics allow firms to project availability and demand and optimize inventories for lending and borrowing. Figure 3: Event-driven application for real time monitoring Summary Financial institutions face significant challenges in reducing settlement duration from two business days (T+2) to one (T+1), particularly when it comes to addressing the existing back-office issues. However, it's crucial for them to achieve this goal within a year as required by the SEC. This blog highlights how MongoDB's developer data platform can help financial institutions automate manual processes and adopt a best practice approach to replace batch processes with a real-time data store repository (ODS). With the help of MongoDB's developer data platform and best practices, financial institutions can achieve operational excellence and meet the SEC's T+1 settlement deadline on May 28, 2024. In the event of T+0 settlement cycles becoming a reality, institutions with the most flexible data platform will be better equipped to adjust. Top banks in the industry are already adopting MongoDB's developer data platform to modernize their infrastructure, leading to reduced time-to-market, lower total cost of ownership, and improved developer productivity. Looking to learn more about how you can modernize or what MongoDB can do for you? Zero downtime migrations using MongoDB’s flexible schema Accelerate your digital transformation with these 5 Phases of Banking Modernization Reduce time-to-market for your customer lifecycle management applications MongoDB’s financial services hub