T-6: MongoDB World's Give Back Week

Dj Walker-Morgan
May 7, 2019 | Updated: July 3, 2019
#MongoDB World 2019

With six weeks to go before MongoDB World 2019, learn how you could be giving to a good cause when you buy your pass this week, get ready for the next weekly challenge, and catch up with the latest talks that have made it into the schedule.

Give Back Week

If you haven’t registered for MongoDB World, the bad news is that you’ve missed the early bird rates. The good news is that if you register this week, you’ll get a discounted ticket and 10% of your ticket price will be donated to Black Girls Code.

That means you get to go to MongoDB World’s three days of information rich talks, sessions and events for less and you get to help fund an organisation dedicated to empowering girls of color between 7 and 17 to become STEM innovators, community leaders and future builders, all through exposing them to computer science and technology.

Head over to the MongoDB World site and register; the discount is automatically applied to all types of ticket. The donation to Black Girls Code is based on that discounted price.

Challenge Update

The first week of Eliot’s MongoDB World Weekly Challenge was a great success - you can read up on how the challenge was solved in this post - Solving The Aggregation Rock Star Challenge. If you get over to the challenge's web site you’ll see the next challenge is tomorrow and involves charting a holiday for engineers.

Talks Talk

There’s still talks being added to the schedule as we finalise speakers and subjects.

Starting up: If you are looking for a quick introduction to the world of MongoDB, check out Don't Panic - The Hitchhiker's Guide to the MongoDB Galaxy, designed specifically to get you started. If you’re looking to get started with the official MongoDB Go driver, there’s Get Going: An Introduction to the Official MongoDB Go Driver to jump start your development.
Scaling up: If you are working at scale, you may want to hear Sharding: Stories From the Field or look at how MongoDB Cluster Design: From Redundancy to GDPR can help you to build out a cluster that suits your needs.
Experience: Talking about real world experience, there’s The Journey of Migration from Oracle to MongoDB at Rakuten and MongoDB Implementation at T-Mobile, where MongoDB users are talking about how they use the database.
Education: MongoDB can both power learning platforms and be taught on them. Learn how in A Tale of Two Use Cases: Innovative MongoDB Solutions for Code Schools.

That's it for T-6, the countdown to MongoDB World 2019 continues with T-5 next week!

← Previous

Solving The Aggregation Rock Star Challenge

The first of Eliot's MongoDB World Weekly Challenges was an out of this world challenge to analyse the records of meteorite impacts. Even if you didn't do the challenge (there's one every Wednesday up to MongoDB World), you can still be a winner because we're going to show you how to get the solution.

May 7, 2019

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