This is where the new MongoDB Atlas Data API comes in. Installing drivers and creating endpoints for your application that can make calls to the database can take time, and if you have a very simple use case, such as just CRUD, this extra overhead is unnecessary. However, there are times when you might not want to use a driver-for example, if it is a purely command-line based application or script, such as one that relies on cURL for sending REST or GraphQL requests via HTTP. Build a RESTful API with Flask, MongoDB, and Python.TypeScript Integration with MongoDB Guide.How to Use MERN Stack: A Complete Guide.Express.js and MongoDB REST API Tutorial.So if you wish to use drivers, this is still a valid option.īelow is a list of some existing tutorials using current drivers, potentially in your language/framework of choice: We have many articles on how to get up and running using MongoDB drivers for your language of choice. In terms of the Online Archive + Cluster unified view via Atlas. You could use MongoDB Compass and go through the connection modal for the online archive and select the Connect to Cluster and Online Archive option. These allow you to call various functions, including covering the Create, Read, Update, Delete (CRUD) operations, from within your project in the language of your choice. It is not currently possible to query the documents storage in Online Archive via Atlas UI. MongoDB has drivers for many different programming languages. The most common way of accessing data from your projects has traditionally been using drivers.
