Shelby Carpenter

3 results

Ruby Added to MongoDB Export to Language for Compass and VS Code

Thousands of developers rely on Compass as a GUI or VS Code as an integrated development environment to query their data in MongoDB. With both Compass and the official MongoDB Extension for VS Code, you can build a query or aggregation using the MongoDB Query API and export it to your chosen programming language. The only limitation? Until now, only four languages have been supported for this feature in both tools: Java, Node.js, C#, and Python. Those four languages cover a significant percentage of the MongoDB developer community, but we knew we wanted to expand to help even more developers export queries/aggregations to their programming language of choice. To this end, we’re pleased to announce that the Export to Language features in both Compass and the VS Code Extension for MongoDB now support exporting to Ruby. To build a query/aggregation in VS Code and export to Ruby, connect to your cluster in VS Code, create a Playground with code that draws on the Query API, and highlight your Query API syntax. From there, you will see a lightbulb icon that gives you the option to export to Ruby, among other languages. You also have the option to export a sample query/aggregation including details on the driver usage so you start with a fully functional code snippet. To build a query/aggregation in Compass and export to Ruby, simply connect to your cluster from Compass, navigate to the “Aggregations” tab, build your query/aggregation, and then click the button with an export icon immediately to the right of the “Save” button. Once you’ve followed the above steps in VS Code or Compass, you’re ready to use the exported code in your Ruby app! For a peek under the hood at how MongoDB’s engineers added Ruby to Compass, check out this great article on Dev.to by Rachelle Palmer , Product Lead for Developer Experience at MongoDB. We hope all the hardcore Rubyists out there find this new feature useful and that it makes it even easier to build Ruby apps with MongoDB. As you continue to use these tools within your application development cycle, don’t hesitate to reach out and give us feedback .

April 1, 2022

Improved Experience for Saved Aggregations and Queries in MongoDB Compass

Tens of thousands of MongoDB users take advantage of MongoDB Compass to query their data and build sophisticated aggregation pipelines. As an easy-to-use GUI, Compass lets you seamlessly connect to and interact with your data, including using our powerful Query API. You just connect to your cluster, navigate to your chosen database and collection, and start building your queries. Many Compass users want to come back again and again to their best queries — or make a query repeatedly available to all database users — but the experience of working with saved queries and aggregations has created some challenges for users in the past. Previously, saved aggregations and queries were bound to a specific database and collection, making it harder to integrate those saved queries and aggregations into the standard software-development lifecycle. If, for example, you built an aggregation pipeline against a staging database and saved it, you’d still have to build that same pipeline again if you wanted to use it for your production database. Users have also reported difficulty finding their favorites after saving them. That’s why we’ve released a new-and-improved experience for saved aggregations and queries in MongoDB Compass. It includes a new “My Queries” screen you can navigate to from the left sidebar or from a tab at the top, next to the “Database” and “Performance” tabs. Once on the “My Queries” screen, you can search across all your saved queries/aggregations and sort or filter by database or collection. And you can apply your saved queries/aggregations across namespaces. To learn more about working with queries and aggregations in Compass, visit our documentation on the Aggregation Pipeline Builder or queries . We’re confident this new experience will make it easier than ever to build, save, and reuse your favorite aggregations and queries, and ultimately remove friction with integrating them into the application development process. Head over to your Compass instance and check it out. (If you’re not yet a Compass user, you can download it for free .) Happy querying!

April 1, 2022

Understanding the MongoDB Stable API and Rapid Release Cadence

MongoDB provides the world’s leading application data platform, and we strive to make it as easy as possible for developers to build and evolve their applications. In MongoDB 5.0, we made two important updates to the way we release database versions and make them available to customers: One was the creation of the Stable API and the other was our new quarterly MongoDB Rapid Release cadence. Now that we have a few Rapid Releases under our belt (visit our blog to learn about MongoDB 5.1 and 5.2 ), we wanted to provide an update on the API and the process for choosing between the Major and Rapid Release tracks. The MongoDB Stable API The Stable API was created to make it easier for customers to upgrade to the latest MongoDB version without worrying about introducing breaking changes to their code base. It includes a subset of MongoDB commands that applications commonly use, and MongoDB ensures those commands remain consistent when we release new database versions. That effectively decouples the application lifecycle from the database lifecycle. Providing this level of consistency is especially important for helping customers consume our innovations faster and take advantage of MongoDB’s new release cadence. It was previously known as the Versioned API, but we changed the name to Stable API to avoid potential confusion. From our conversations with users and customers, it became clear that the previous name gave the impression that the API would change with each incremental MongoDB version release. That is not the case, so we say “hello” to the MongoDB Stable API. The MongoDB Rapid Release Cadence MongoDB Atlas customers with clusters on a Dedicated Tier (M10+) can opt in to Rapid Releases to get the latest features from MongoDB on a quarterly basis. Atlas customers are initially on the Major Release track; Major Releases happen annually and contain the previous year’s Rapid Releases by default. Customers who choose the Major Release track will have the following upgrade flow: 5.0 -> 6.0 -> 7.0, etc., and can schedule when they want to upgrade to each new Major Release after it enters general availability. Customers who opt in to the Rapid Release track will have the following upgrade flow: 5.0 -> 5.1 -> 5.2 -> 5.3 -> 6.0 -> 6.1 -> 6.2, etc. If you are on a Major Release and decide to change tracks, then you will automatically go to the next Rapid Release. (If you are on 6.0 and 6.2 is the latest Rapid Release, you can jump directly from 6.0 to 6.2 without having to upgrade to 6.1 first.) Customers on the Major Release track will still receive regular patch upgrades. Users on the Rapid Release track who later decide to opt out will need to do so at the time of the next Major Release. If you’re MongoDB 5.2 and want to change back to the Major Release track, for example, you will wait to leave the Rapid Release track until the next Major Release, MongoDB 6.0, is available. As another example, at the time of publication, the latest Major Release is 5.0 and the latest Rapid Release is 5.2. A customer on MongoDB 4.4 (an earlier Major Release prior to the new release cadence and numbering scheme ) would need to manually upgrade from 4.4 to 5.0 before opting in to Rapid Releases and getting MongoDB 5.2. To opt in to the Rapid Release cadence, choose the “Latest Release” option in the Atlas web UI. Rapid Releases are only supported for MongoDB Atlas. For on-premises environments, they should be used only for development builds and testing and not for production environments. Apart from MongoDB Atlas Dedicated Tier clusters, Atlas supports Shared Tier clusters M0, M2, and M5 — which provide 512MB, 2GB, and 5GB of storage, respectively — as well as managed serverless instances , which are currently in public preview. Shared Tier clusters are always on the Major Release track, and serverless instances are on the Rapid Release track. With options to get Major or Rapid Releases in MongoDB Atlas and to use the Stable API for consistency across versions, MongoDB customers have more flexibility than ever to choose how to take advantage of the latest MongoDB database upgrades. Stay tuned for the latest innovations from MongoDB in the 5.3 release this spring, and join us at MongoDB World this summer to learn about MongoDB 6.0 and more!

March 10, 2022