Today at MongoDB World 2018 in New York, we are excited to announce the beta release of MongoDB Charts, available now.
MongoDB Charts is the fastest and easiest way to build visualizations of MongoDB data. Now you can easily build visualizations with an intuitive UI and analyze complex, nested data—like arrays and subdocuments—something other visualization technologies designed for tabular databases struggle with. Then assemble those visualizations into a dashboard for at-a-glance, up-to-the minute information. Dashboards can be shared with other users, either for collaboration or viewing only, so that entire groups and organizations can become data-driven and benefit from data visualizations and the insights they provide. When you connect to a live data source, MongoDB Charts will keep your charts and dashboards up to date with the most recent data.
Charts allows you to connect to any MongoDB instance on which you have access permissions, or use existing data sources that other Charts users share with you. With MongoDB’s workload isolation capabilities—enabling you to separate your operational from analytical workloads in the same cluster—you can use Charts for a real-time view without having any impact on production workloads.
Unlike other visualization products, MongoDB Charts is designed to natively handle MongoDB’s rich data structures. MongoDB Charts makes it easy to visualize complex arrays and subdocuments without flattening the data or spending time and effort on ETL. Charts will automatically generate an aggregation pipeline from your chart design which is executed on your MongoDB server, giving you full access to the power of MongoDB when creating visualizations.
Charts already supports all common visualization types, including bar, column, line, area, scatter and donut charts, with table views and other advanced charts coming soon. Multiple visualizations can be assembled into dashboards, providing an at-a-glance understanding of all of your most important data. Dashboards can be used to track KPIs, understand trends, spot outliers and anomalies, and more.
Graphs and charts are a great way to communicate insights with others, but we know data can often be sensitive. Charts lets you stay in control over which users in your organization have access to your data sources and dashboards. You can choose to share with your entire organization, select individuals or keep things private to yourself. Dashboards can be shared as read-only or as read-write, depending on whether you want to communicate or collaborate.
Since this is a beta release, it’s free for anyone to try, but keep in mind that we may add or change functionality before the final release. MongoDB Charts is available as a Docker image which you can install on a server or VM within your environment. Once the Docker container is running, people in your organisation can access Charts from any desktop web browser. To download the image and get started with Charts, head to the MongoDB Download Center.
We think that MongoDB Charts is the best way to get quick, self-service visualizations of the data you’re storing in MongoDB. But we’re only just getting started. Once you try out the beta, please use the built-in feedback tool to report issues and to let us know what you do and don’t like, and we’ll use this input to make future releases even better.
The development, release, and timing of any features or functionality described for our products remains at our sole discretion. This information is merely intended to outline our general product direction and it should not be relied on in making a purchasing decision nor is this a commitment, promise or legal obligation to deliver any material, code, or functionality.
Introducing the MongoDB Enterprise Operator for Kubernetes and OpenShift
Today more DevOps teams are leveraging the power of containerization, and technologies like Kubernetes and Red Hat OpenShift, to manage containerized database clusters. To support teams building cloud-native apps with Kubernetes and OpenShift, we are introducing a Kubernetes Operator (beta) that integrates with Ops Manager, the enterprise management platform for MongoDB. The operator enables a user to deploy and manage MongoDB clusters from the Kubernetes API, without having to manually configure them in Ops Manager. With this Kubernetes integration, you can consistently and effortlessly run and deploy workloads wherever they need to be, standing up the same database configuration in different environments, all controlled with a simple, declarative configuration. Operations teams can also offer developers new services like MongoDB-as-a-Service, that could provide for them a fully managed database, alongside other products and services, managed by Kubernetes and OpenShift. In this blog, we’ll cover the following: Brief discussion on the container revolution Overview of MongoDB Ops Manager How to Install and configure the MongoDB Enterprise Operator for Kubernetes Troubleshooting Where to go for more information The containerization movement If you ever visited an international shipping port or drove down an interstate highway you may have seen large rectangular metal containers generally referred to as intermodal containers. These containers are designed and built using the same specifications even though the contents of these boxes can vary greatly. The consistent design not only enables these containers to freely move from ship, to rail, and to truck, they also allow this movement without unloading and reloading the cargo contents. This same concept of a container can be applied to software applications where the application is the contents of the container along with its supporting frameworks and libraries. The container can be freely moved from one platform to another all without disturbing the application. This capability makes it easy to move an application from an on-premise datacenter server to a public cloud provider, or to quickly stand up replica environments for development, test, and production usage. MongoDB 4.0 introduces the MongoDB Enterprise Operator for Kubernetes which enables a user to deploy and manage MongoDB clusters from the Kubernetes API, without the user having to connect directly to Ops Manager or Cloud Manager (the hosted version of Ops Manager, delivered as a service . While MongoDB is fully supported in a containerized environment, you need to make sure that the benefits you get from containerizing the database exceed the cost of managing the configuration. As with any production database workload, these containers should use persistent storage and will require additional configuration depending on the underlying container technology used. To help facilitate the management of the containers themselves, DevOps teams are leveraging the power of orchestration technologies like Kubernetes and Red Hat OpenShift. While these technologies are great at container management, they are not aware of application specific configurations and deployment topologies such as MongoDB replica sets and sharded clusters. For this reason, Kubernetes has Custom Resources and Operators which allow third-parties to extend the Kubernetes API and enable application aware deployments. Later in this blog you will learn how to install and get started with the MongoDB Enterprise Operator for Kubernetes. First let’s cover MongoDB Ops Manager, which is a key piece in efficient MongoDB cluster management. Managing MongoDB Ops Manager is an enterprise class management platform for MongoDB clusters that you run on your own infrastructure. The capabilities of Ops Manager include monitoring, alerting, disaster recovery, scaling, deploying and upgrading of replica sets and sharded clusters, and other MongoDB products, such as the BI Connector. While a thorough discussion of Ops Manager is out of scope of this blog it is important to understand the basic components that make up Ops Manager as they will be used by the Kubernetes Operator to create your deployments.. Figure 1: MongoDB Ops Manager deployment screen A simplified Ops Manager architecture is shown in Figure 2 below. Note that there are other agents that Ops Manager uses to support features like backup but these are outside the scope of this blog and not shown. For complete information on MongoDB Ops Manager architecture see the online documentation found at the following URL: https://docs.opsmanager.mongodb.com/current/ Figure 2: Simplified Ops Manager deployment The MongoDB HTTP Service provides a web application for administration. These pages are simply a front end to a robust set of Ops Manager REST APIs that are hosted in the Ops Manager HTTP Service. It is through these REST APIs that the Kubernetes Operator will interact with Ops Manager. MongoDB Automation Agent With a typical Ops Manager deployment there are many management options including upgrading the cluster to a different version, adding secondaries to an existing replica set and converting an existing replica set into a sharded cluster. So how does Ops Manager go about upgrading each node of a cluster or spinning up new MongoD instances? It does this by relying on a locally installed service called the Ops Manager Automation Agent which runs on every single MongoDB node in the cluster. This lightweight service is available on multiple operating systems so regardless if your MongoDB nodes are running in a Linux Container or Windows Server virtual machine or your on-prem PowerPC Server, there is an Automation Agent available for that platform. The Automation Agents receive instructions from Ops Manager REST APIs to perform work on the cluster node. MongoDB Monitoring Agent When Ops Manager shows statistics such as database size and inserts per second it is receiving this telemetry from the individual nodes running MongoDB. Ops Manager relies on the Monitoring Agent to connect to your MongoDB processes, collect data about the state of your deployment, then send that data to Ops Manager. There can be one or more Monitoring Agents deployed in your infrastructure for reliability but only one primary agent per Ops Manager Project is collecting data. Ops Manager is all about automation and as soon as you have the automation agent deployed, other supporting agents like the Monitoring agent are deployed for you. In the scenario where the Kubernetes Operator has issued a command to deploy a new MongoDB cluster in a new project, Ops Manager will take care of deploying the monitoring agent into the containers running your new MongoDB cluster. Getting started with MongoDB Enterprise Operator for Kubernetes Ops Manager is an integral part of automating a MongoDB cluster with Kubernetes. To get started you will need access to an Ops Manager 4.0+ environment or MongoDB Cloud Manager. The MongoDB Enterprise Operator for Kubernetes is compatible with Kubernetes v1.9 and above. It also has been tested with Openshift version 3.9. You will need access to a Kubernetes environment. If you do not have access to a Kubernetes environment, or just want to stand up a test environment, you can use minikube which deploys a local single node Kubernetes cluster on your machine. For additional information and setup instructions check out the following URL: https://kubernetes.io/docs/setup/minikube . The following sections will cover the three step installation and configuration of the MongoDB Enterprise Operator for Kubernetes. The order of installation will be as follows: Step 1: Installing the MongoDB Enterprise Operator via a helm or yaml file Step 2: Creating and applying a Kubernetes ConfigMap file Step 3: Create the Kubernetes secret object which will store the Ops Manager API Key Step 1: Installing MongoDB Enterprise Operator for Kubernetes To install the MongoDB Enterprise Operator for Kubernetes you can use helm, the Kubernetes package manager, or pass a yaml file to kubectl. The instructions for both of these methods is as follows, pick one and continue to step 2. To install the operator via Helm: To install with Helm you will first need to clone the public repo https://github.com/mongodb/mongodb-enterprise-kubernetes.git Change directories into the local copy and run the following command on the command line: helm install helm_chart/ --name mongodb-enterprise To install the operator via a yaml file: Run the following command from the command line: kubectl apply -f https://raw.githubusercontent.com/mongodb/mongodb-enterprise-kubernetes/master/mongodb-enterprise.yaml At this point the MongoDB Enterprise Operator for Kubernetes is installed and now needs to be configured. First, we must create and apply a Kubernetes ConfigMap file. A Kubernetes ConfigMap file holds key-value pairs of configuration data that can be consumed in pods or used to store configuration data. In this use case the ConfigMap file will store configuration information about the Ops Manager deployment we want to use. Step 2: Creating the Kubernetes ConfigMap file For the Kubernetes Operator to know what Ops Manager you want to use you will need to obtain some properties from the Ops Manager console and create a ConfigMap file. These properties are as follows: Base Url - The URL of your Ops Manager or Cloud Manager. Project Id - The id of an Ops Manager Project which the Kubernetes Operator will deploy into. User - An existing Ops Manager username Public API Key - Used by the Kubernetes Operator to connect to the Ops Manager REST API endpoint If you already know how to obtain these follows copy them down and proceed to Step 3. Base Url The Base Uri is the URL of your Ops Manager or Cloud Manager. Note: If you are using Cloud Manager the Base Url is, “ https://cloud.mongodb.com ” To obtain the Base Url in Ops Manager copy the Url used to connect to your Ops Manager server from your browser's navigation bar. It should be something similar to http://servername:8080. You can also perform the following: Login to Ops Manager and click on the Admin button. Next select the “Ops Manager Config” menu item. You will be presented with a screen similar to the figure below: Figure 3: Ops Manager Config page Copy down the value displayed in the URL To Access Ops Manager box. Note: If you don’t have access to the Admin drop down you will have to copy the Url used to connect to your Ops Manager server from your browser's navigation bar. Project Id The Project Id is the id of an Ops Manager Project which the Kubernetes Operator will deploy into. An Ops Manager Project is a logical organization of MongoDB clusters and also provides a security boundary. One or more Projects are apart of an Ops Manager Organization. If you need to create an Organization click on your user name at the upper right side of the screen and select, “Organizations”. Next click on the “+ New Organization” button and provide a name for your Organization. Once you have an Organization you can create a Project. Figure 4: Ops Manager Organizations page To create a new Project, click on your Organization name. This will bring you to the Projects page and from here click on the “+ New Project” button and provide a unique name for your Project. If you are not an Ops Manager administrator you may not have this option and will have to ask your administrator to create a Project. Once the Project is created or if you already have a Project created on your behalf by an administrator you can obtain the Project Id by clicking on the Settings menu option as shown in the Figure below. Figure 5: Project Settings page Copy the Project ID. User The User is an existing Ops Manager username To see the list of Ops Manager users return to the Project and click on the “Users & Teams” menu. You can use any Ops Manager user who has at least Project Owner access. If you’d like to create another username click on the “Add Users & Team” button as shown in Figure 6. Figure 6: Users & Teams page Copy down the email of the user you would like the Kubernetes Operator to use when connecting to Ops Manager. Public API Key The Ops Manager API Key is used by the Kubernetes Operator to connect to the Ops Manager REST API endpoint. You can create a API Key by clicking on your username on the upper right hand corner of the Ops Manager console and selecting, “Account” from the drop down menu. This will open the Account Settings page as shown in Figure 7. Figure 7: Public API Access page Click on the “Public API Access” tab. To create a new API key click on the “Generate” button and provide a description. Upon completion you will receive an API key as shown in Figure 8. Figure 8: Confirm API Key dialog Be sure to copy the API Key as it will be used later as a value in a configuration file. It is important to copy this value while the dialog is up since you can not read it back once you close the dialog . If you missed writing the value down you will need to delete the API Key and create a new one. Note: If you are using MongoDB Cloud Manager or have Ops Manager deployed in a secured network you may need to whitelist the IP range of your Kubernetes cluster so that the Operator can make requests to Ops Manager using this API Key. Now that we have acquired the necessary Ops Manager configuration information we need to create a Kubernetes ConfigMap file for the Kubernetes Project. To do this use a text editor of your choice and create the following yaml file, substituting the bold placeholders for the values you obtained in the Ops Manager console. For sample purposes we can call this file “my-project.yaml”. apiVersion: v1 kind: ConfigMap metadata: name: namespace: mongodb data: projectId: baseUrl: Figure 9: Sample ConfigMap file Note: The format of the ConfigMap file may change over time as features and capabilities get added to the Operator. Be sure to check with the MongoDB documentation if you are having problems submitting the ConfigMap file. Once you create this file you can apply the ConfigMap to Kubernetes using the following command: kubectl apply -f my-project.yaml Step 3: Creating the Kubernetes Secret For a user to be able to create or update objects in an Ops Manager Project they need a Public API Key. Earlier in this section we created a new API Key and you hopefully wrote it down. This API Key will be held by Kubernetes as a Secret object. You can create this Secret with the following command: kubectl -n mongodb create secret generic --from-literal="user= " --from-literal="publicApiKey= " Make sure you replace the User and Public API key values with those you obtained from your Ops Manager console. You can pick any name for the credentials – just make a note of it as you will need it later when you start creating MongoDB clusters. Now we're ready to start deploying MongoDB Clusters! Deploying a MongoDB Replica Set Kubernetes can deploy a MongoDB standalone, replica set or a sharded cluster. To deploy a 3 node replica set create the following yaml file: apiVersion: mongodb.com/v1 kind: MongoDbReplicaSet metadata: name: namespace: mongodb spec: members: 3 version: 3.6.5 persistent: false project: credentials: Figure 10: simple-rs.yaml file describing a three node replica set The name of your new cluster can be any name you chose. The name of the OpsManager Project config map and the name of credentials secret were defined previously. To submit the request for Kubernetes to create this cluster simply pass the name of the yaml file you created to the following kubectl command: kubectl apply -f simple-rs.yaml After a few minutes your new cluster will show up in Ops Manager as shown in Figure 11. Figure 11: Servers tab of the Deployment page in Ops Manager Notice that Ops Manager installed not only the Automation Agents on these three containers running MongoDB, it also installed Monitoring Agent and Backup Agents. A word on persistent storage What good would a database be if anytime the container died your data went to the grave as well? Probably not a good situation and maybe one where tuning up the resumé might be a good thing to do as well. Up until recently, the lack of persistent storage and consistent DNS mappings were major issues with running databases within containers. Fortunately, recent work in the Kubernetes ecosystem has addressed this concern and new features like PersistentVolumes and StatefulSets have emerged allowing you to deploy databases like MongoDB without worrying about losing data because of hardware failure or the container moved elsewhere in your datacenter. Additional configuration of the storage is required on the Kubernetes cluster before you can deploy a MongoDB Cluster that uses persistent storage. In Kubernetes there are two types of persistent volumes: static and dynamic. The Kubernetes Operator can provision MongoDB objects (i.e. standalone, replica set and sharded clusters) using either type. Connecting your application Connecting to MongoDB deployments in Kubernetes is no different than other deployment topologies. However, it is likely that you'll need to address the network specifics of your Kubernetes configuration. To abstract the deployment specific information such as hostnames and ports of your MongoDB deployment, the Kubernetes Enterprise Operator for Kubernetes uses Kubernetes Services. Services Each MongoDB deployment type will have two Kubernetes services generated automatically during provisioning. For example, suppose we have a single 3 node replica set called "my-replica-set", then you can enumerate the services using the following statement: kubectl get all -n mongodb --selector=app=my-replica-set-svc This statement yields the following results: NAME READY STATUS RESTARTS AGE pod/my-replica-set-0 1/1 Running 0 29m pod/my-replica-set-1 1/1 Running 0 29m pod/my-replica-set-2 1/1 Running 0 29m NAME TYPE CLUSTER-IP EXTERNAL-IP PORT(S) AGE service/my-replica-set-svc ClusterIP None 27017/TCP 29m service/my-replica-set-svc-external NodePort 10.103.220.236 27017:30057/TCP 29m NAME DESIRED CURRENT AGE statefulset.apps/my-replica-set 3 3 29m Note the appended string "-svc" to the name of the replica set. The service with "-external" is a NodePort - which means it's exposed to the overall cluster DNS name on port 30057. Note: If you are using Minikube you can obtain the IP address of the running replica set by issuing the following: minikube service list In our example which used minikube the result set contained the following information: mongodb my-replica-set-svc-external http://192.168.39.95:30057 Now that we know the IP of our MongoDB cluster we can connect using the Mongo Shell or whatever application or tool you would like to use. Basic Troubleshooting If you are having problems submitting a deployment you should read the logs. Issues like authentication issues and other common problems can be easily detected in the log files. You can view the MongoDB Enterprise Operator for Kubernetes log files via the following command: kubectl logs -f deployment/mongodb-enterprise-operator -n mongodb You can also use kubectl to see the logs of the database pods. The main container processes is continually tailing the Automation Agent logs and can be seen with the following statement: kubectl logs -n mongodb Note: You can enumerate the list of pods using kubectl get pods -n mongodb Another common troubleshooting technique is to shell into one of the containers running MongoDB. Here you can use common Linux tools to view the processes, troubleshoot, or even check mongo shell connections (sometimes helpful in diagnosing network issues). kubectl exec -it -n mongodb -- /bin/bash An example output of this command is as follows: UID PID PPID C STIME TTY TIME CMD mongodb 1 0 0 16:23 ? 00:00:00 /bin/sh -c supervisord -c /mongo mongodb 6 1 0 16:23 ? 00:00:01 /usr/bin/python /usr/bin/supervi mongodb 9 6 0 16:23 ? 00:00:00 bash /mongodb-automation/files/a mongodb 25 9 0 16:23 ? 00:00:00 tail -n 1000 -F /var/log/mongodb mongodb 26 1 4 16:23 ? 00:04:17 /mongodb-automation/files/mongod mongodb 45 1 0 16:23 ? 00:00:01 /var/lib/mongodb-mms-automation/ mongodb 56 1 0 16:23 ? 00:00:44 /var/lib/mongodb-mms-automation/ mongodb 76 1 1 16:23 ? 00:01:23 /var/lib/mongodb-mms-automation/ mongodb 8435 0 0 18:07 pts/0 00:00:00 /bin/bash From inside the container we can make a connection to the local MongoDB node easily by running the mongo shell via the following command: /var/lib/mongodb-mms-automation/mongodb-linux-x86_64-3.6.5/bin/mongo --port 27017 Note: The version of the automation agent may be different than 3.6.5, be sure to check the directory path Where to go for more information More information will be available on the MongoDB documentation website in the near future. Until then check out these resources for more information: Slack: #enterprise-kubernetes Sign up @ https://launchpass.com/mongo-db GitHub: https://github.com/mongodb/mongodb-enterprise-kubernetes To see all MongoDB operations best practices, download our whitepaper: https://www.mongodb.com/collateral/mongodb-operations-best-practices
Sales Development Series: Meet the North America Account Development Team
Sales Development is a crucial part of the Sales organization at MongoDB. Our Sales Development function is broken down into Sales Development Representatives (SDRs), who qualify and validate inbound opportunities from both existing and prospective customers, and Account Development Representatives (ADRs), who support outbound opportunities by planning and executing pipeline generation strategies. Both of these roles offer an excellent path to kickstarting your career in sales at MongoDB. In this blog post, you’ll learn more about our North American outbound team, which is divided into territories covering North America West, North America Central, New York City and the Mid-Atlantic, and New England, East Canada, and the South East. Hear from Regional Manager Jordan Gregory and a few Account Development Representatives about the ADR role and how MongoDB’s sales culture enables employees to grow and succeed in their career. An overview of Account Development in North America Jordan Gregory , Regional Manager of Sales Development for New England, East Canada, and the South East Account Development at MongoDB is crucial to the success of our sales organization, being the first point of contact with all of our prospective customers. We partner with our incredibly talented Enterprise Account Executives to find new business opportunities within some of the largest and most complex organizations in the world across a broad range of industries (financial institutions, video games, telecommunications, insurance - you name it!). The Account Development team culture is one of extreme ownership. It’s about controlling what we can control, building off of each other’s strengths, enjoying working together, and holding ourselves and each other accountable for growing and failing forward every day. If you work hard, you play hard, and that culminates in a lot of fun with this incredible group! MongoDB has a growth-focused culture. Our management and Sales leadership team take learning and development seriously, and the most successful individuals on the Sales team are those who are committed to growing and learning in their role. MongoDB is an open-source data platform company, and I firmly believe that if you can sell an open-source data platform, you can sell anything. This is one of the most challenging places to sell and because of that, and the focus on growth and development, I’ve seen countless people (including myself) take their careers to new heights. The hardest part of sales is prospecting, and it’s something we train our ADRs on extensively. You’ll learn how to identify your Ideal Customer Profile, execute deep discovery and qualification, and progress deals forward to Qualified Pipeline. You’ll also go through our Sales Bootcamp and on-the-job training. Another product of the ADR program is the massive impact we have on revenue which allows folks to build their internal brand and make lifelong connections. On top of that, we have structured upskill programs to set our ADRs up for success in the next role that they’re pursuing internally, whether that's as a Cloud Account Executive, an Associate Account Executive, or other non-direct sales roles like Customer Success and Field Marketing. We’ve also had internal promotions from the Sales Development org to Sales Enablement. At MongoDB, there is a lot of mobility to progress your career in the direction you want, and you’ll be truly valued as a person rather than an employee number or a revenue target. Hear from some team members Andrew Brownlee , Account Development Representative for New York City I joined MongoDB because it seemed like a great place to start my journey to being an Enterprise Sales Executive in the software industry. The people here have a winning mentality and operate as a team when faced with a challenge. The products are world-class and we invest heavily in R&D. MongoDB also has a process called BDR to CRO that’s geared towards developing and promoting sales talent year over year. The most exciting part about working here is the opportunity ahead. To be successful at MongoDB takes conviction, drive, and curiosity. You have to be firm in your opinion that our technology can transform an organization for the best. You must have the drive to push when it's easy, and when it's hard. The best ADRs are focused on being effective with their activity day-to-day and aren't dissuaded by how easy or hard that particular quarter is. Curiosity will help you grow in your career. It’ll also help you get the respect you need amongst your stakeholders. Maria Dorsey , Account Development Representative for North America Central I joined MongoDB because I was looking for a challenging yet rewarding start to my software sales career. It was clear to me throughout the MongoDB interview process that there is a huge emphasis on growth and development which is exactly what I was looking for. During my onboarding, I received a lot of support from my team. Although learning the MongoDB value proposition, products, and sales process can seem overwhelming, my team set aside time to ensure I was ramping up successfully. My manager also took the time to listen to my concerns, talk through tech fundamentals, walk through use cases I was unfamiliar with, and was an ally that I could depend on. What makes me stay at MongoDB is the opportunity for growth, the culture of the Sales Development organization, and the collaboration with enterprise reps and management. I’ve been extremely lucky to learn from and work alongside Enterprise Account Executives, Regional Directors, and my Regional Vice President who all truly care about my growth and success. The biggest thing that makes someone successful as an ADR is their willingness and eagerness to learn. MongoDB doesn’t necessarily care if you come from a software sales background (some of the best ADRs have not), but rather your ability and eagerness to learn the tech, sales process, and stakeholder management. These characteristics are a great foundation for building a long successful career at MongoDB. Vlad Pak , Account Development Representative for North America West I joined MongoDB because I wanted to challenge myself and gain experience working in enterprise sales. MongoDB is an incredible company that offers many opportunities for personal, professional, and financial growth, but the thing that keeps me happy here is the culture. I am surrounded by driven and intelligent teammates and leadership that cares about my success. It's great to be supported from an employee-first perspective. I think the two key traits that make someone successful on my team and in my role are proactiveness and curiosity. Many of our team members are proactively sharing insights, collaborating, and facilitating engagement with each other which benefits us all and drives us to be the best ADRs we can be. Curiosity is the bread and butter of any successful sales professional and will directly impact the quantity and quality of the meetings we set, helping us attain our quotas! I am looking forward to growing my career with MongoDB in a closing role and taking on the challenge of owning my own sales cycle. It’s exciting to work for a company that is leading the charge in digital transformation and changing the way enterprises approach technological innovation. It has been a great learning experience so far, and I can’t wait to see how the organization will grow and evolve along with my career! Interested in joining the sales team at MongoDB? We have several open roles on our team and would love for you to transform your career with us!