MongoDB Logo
Nominate a project for the MongoDB Innovation Awards today!

MongoDB 1.8 Released

MongoDB
March 16, 2011
#Releases

We are happy to announce that MongoDB v1.8.0 is now available. 1.8 is the stable follow-up release to 1.6, which came out in August of 2010. Version 1.8 introduces many new features, along with bug fixes and other improvements. Some of the highlights:

A journaling storage engine has been one of the most requested and discussed features within the MongoDB community, and we’re happy to announce that journaling is now available. With journaling enabled, crash recovery is fast and safe.

There were no major changes to sharding, but this release includes many internal improvements, making for a vastly improved experience. As an example, splitting and balancing are considerably faster, with less impact on the overall system.

Downloads: http://www.mongodb.org/downloads
Release Notes: http://www.mongodb.org/display/DOCS/1.8+Release+Notes
Full change log: http://jira.mongodb.org/secure/IssueNavigator.jspa?requestId=10128

We hosted a webinar on 3/17 providing more details on what’s new in MongoDB v1.8. The recording and slides are available on 10gen.com.

Thanks to the MongoDB user community for providing feedback and for testing through the 1.7.x development series.

← Previous

MongoDB European conferences next week

There’s just a week to go before our European conferences, when over 400 members of the MongoDB community will gather in London, Paris, and Berlin. The level of interest in and enthusiasm for MongoDB is really exciting. There are just a few places left if you still want to attend either the London and Berlin events. Paris is now sold out but we are taking names for the waiting list. 10gen founder Eliot Horowitz, and several of the key engineers developing the MongoDB project will be presenting sessions aimed at developers and administrators interested in learning how to use the database, with sessions on schema design, indexing, administration, deployment strategies, scaling, and other features. You will also get to hear from several companies about some of the ways in which they are using MongoDB. Here’s just a taste of some of those sessions planned: Graham Tackley of Guardian News and Media will talk about why the Guardian chose MongoDB for guardian.co.uk David Mytton, Founder, Boxed Ice, who use MongoDB to handle billions of database documents, will talk about monitoring MongoDB. Russell Smith, UKD1 Limited, will cover Geo & capped collections with MongoDB - use cases & performance in the real world. Martin Tepper, Travel IQ will explain the architectural problems, and how Travel IQ solved them by using MongoDB as a layer on top of their RDBMS. Lennart Koopmann, XING, will talk about how MongoDB capped collections are perfect for logging. Lennart built his project Graylog2 on top of a capped collection and will talk about his experiences, what you can do with them and what they are good at. Maxime Topolov will talk about how freerice.com, a Drupal site is using MongoDB to serve over 20 Millions page views per day. François de Metz & Ori Pekelman, AF83, will talk about how UCEngine, an Open Source Unified Communication and Collaboration application toolkit, is using MongoDB to store event data in an effecient way. Victor Goya, one of the core developer of UC Engine, will provide an overview of the architecture of UCEngine and a detailed feedback on how it benefits from MongoDB. The conferences are also a great opportunity to meet with and discuss your interest in or usage of MongoDB with the 10gen team and other MongoDB users. We are really looking forward to catching up with you next week, both during the conferences and and at the after parties! :-) MongoUK 2011, 21st March Mongo France 2011, 23rd March Mongo Germany 2011, 25th March Special thanks to Skills Matter in London and AF83 and La Cantine in Paris for their support and partnership for these events. Finally, there are some slots open for lightning talks in London and Berlin. Please contact meghan@10gen.com if you are interested in presenting. We look forward to seeing you next week!

March 15, 2011
Next →

Introducing: Atlas Operator for Kubernetes

The MongoDB Enterprise Operator serves to automate and manage MongoDB clusters on self-managed infrastructure. While this integration has provided complete control over self-managed MongoDB deployments from a single Kubernetes control plane, we’re taking it a step further by extending this functionality to our fully-managed database—MongoDB Atlas. We’re excited to introduce the trial version of the Atlas Operator for Kubernetes. The Atlas Operator will allow you to manage all your MongoDB Atlas clusters without ever having to leave Kubernetes. Keep your workflow as seamless and optimized as possible by managing the lifecycle of your cloud-native applications from where you want most. With the trial version of this Atlas Operator, you can provision and deploy fully-managed MongoDB Atlas clusters on the cloud provider of your choice through Kubernetes. This provider is especially important for those seeking to unlock the power of multi-cloud with unique tools and services native to AWS, Google Cloud, and Azure without any added complexity to the data management experience. With this new Atlas Operator, you get the best of all clouds with multi-cloud clusters on Atlas , coupled with the freedom to run your entire stack anywhere, all while managed in one central location. The “trial version” simply means it has all the core functionality to provision fully-managed Atlas clusters, but the bells and whistles are yet to come. In addition to encapsulating core Atlas functionality, it ensures Kubernetes Secrets are created for each database user which allows for easier management of sensitive data. The Atlas Operator also allows you to create IP Bindings so your applications can securely access clusters. If you’re interested in using the trial version of the Atlas Operator today, follow our quickstart guide below to get started! Quickstart Below you’ll find the steps to create your first cluster in Atlas using the Atlas Operator. Note that you need to have a running Kubernetes cluster before deploying the Atlas Operator. Register/Login to Atlas and create API Keys for your Organization. This information together with the Organization ID will be used to configure the Atlas Operator access to Atlas. Deploy the Atlas Operator kubectl apply -f \ https://raw.githubusercontent.com/mongodb/mongodb-atlas-kubernetes/main/deploy/all-in-one.yaml Create a Secret containing connection information from step one. This Secret will be used by the Atlas Operator to connect to Atlas: kubectl create secret generic mongodb-atlas-operator-api-key \ --from-literal="orgId=<the_atlas_organization_id>" \ --from-literal="publicApiKey=<the_atlas_api_public_key>" \ --from-literal="privateApiKey=<the_atlas_api_private_key>" \ -n mongodb-atlas-system Create AtlasProject Custom Resource: cat <<EOF | kubectl apply -f - apiVersion: atlas.mongodb.com/v1 kind: AtlasProject metadata: name: my-project spec: name: Test Atlas Operator Project projectIpAccessList: - ipAddress: "0.0.0.0/0" comment: "Allowing access to database from everywhere (only for Demo!)" EOF Create AtlasCluster Custom Resource cat <<EOF | kubectl apply -f - apiVersion: atlas.mongodb.com/v1 kind: AtlasCluster metadata: name: my-atlas-cluster spec: name: "Test-cluster" projectRef: name: my-project providerSettings: instanceSizeName: M10 providerName: AWS regionName: US_EAST_1 EOF (You'll have to wait until the cluster is ready - "status" field shows "ready:true":) kubectl get atlasclusters my-atlas-cluster -o=jsonpath='{.status.conditions[?(@.type=="Ready")].status}' True Create a Secret for the password that will be used to log into Atlas Cluster Database kubectl create secret generic the-user-password \ --from-literal="password=P@@sword%" Create AtlasDatabaseUser Custom Resource (references the password Secret) cat <<EOF | kubectl apply -f - apiVersion: atlas.mongodb.com/v1 kind: AtlasDatabaseUser metadata: name: my-database-user spec: roles: - roleName: "readWriteAnyDatabase" databaseName: "admin" projectRef: name: my-project username: theuser passwordSecretRef: name: the-user-password EOF Shortly the Secret will be created by the Atlas Operator containing the data necessary to connect to the Atlas Cluster. You can mount it into your application Pod and read the connection strings from the file or from the environment variable. kubectl get secrets/test-atlas-operator-project-test-cluster-theuser \ -o=jsonpath="{.data.connectionString.standardSrv}} | base64 -d mongodb+srv://theuser:P%40%40sword%25@test-cluster.peqtm.mongodb.net Stay Tuned for More Be on the lookout for updates in future blog posts! The trial version of the MongoDB Atlas Operator is currently available on multiple marketplaces, but we’ll be looking to make enhancements in the near future. For more information, check out our MongoDB Atlas & Kubernetes GitHub page and our documentation .

April 8, 2021