Getting Started With Azure Spring Apps and MongoDB Atlas: A Step-by-Step Guide
Rate this tutorial
Embrace the fusion of cloud computing and modern application development as we delve into the integration of Azure
Spring Apps
and MongoDB. In this tutorial, we'll guide you through the process of creating
and deploying a Spring Boot
application in the Azure Cloud, leveraging the strengths of Azure's platform, Spring Boot's simplicity, and MongoDB's
capabilities.
Whether you're a developer venturing into the cloud landscape or looking to refine your cloud-native skills, this
step-by-step guide provides a concise roadmap. By the end of this journey, you'll have a fully functional Spring Boot
application seamlessly running on Azure Spring
Apps, with MongoDB handling your data storage needs and a REST API ready
for interaction. Let's explore the synergy of these technologies and propel your cloud-native endeavors forward.
- Java 17
- Maven 3.8.7
- Git (or you can download the zip folder and unzip it locally)
- MongoDB Atlas cluster (the M0 free tier is enough for this tutorial). If you don't have one, you can create one for free.
- Install the Azure CLI to be able to deploy your Azure Spring App.
I'm using Debian, so I just had to run a single command line to install the Azure CLI. Read the documentation for your
operating system.
Once it's installed, you should be able to run this command.
It should return something like this.
Note: It's normal if you don't have the Spring extension yet. We'll install it in a minute.
You can log into your Azure account using the following command.
It should open a web browser in which you can authenticate to Azure. Then, the command should print something like this.
Once you are logged into your Azure account, you can type the following command to install the Spring extension.
To begin with, on the home page of Azure, click on
Create a resource.
Then, select Azure Spring Apps in the marketplace.
Create a new Azure Spring App.
Now, you can select your subscription and your resource group. Create a new one if necessary. You can also create a
service name and select the region.
For the other options, you can use your best judgment depending on your situation but here is what I did for this
tutorial, which isn't meant for production use...
- Basics:
- Hosting: "Basic" (not for production use, but it's fine for me)
- Zone Redundant: Disable
- Deploy sample project: No
- Diagnostic settings:
- Enable by default.
- Application Insights:
- Disable (You probably want to keep this in production)
- Networking:
- Deploy in your own virtual network: No
- Tags:
- I didn't add any
Here is my
Review and create summary:
Once you are happy, click on
Create and wait a minute for your deployment to be ready to use.In this tutorial, we are deploying
this Java, Spring Boot, and MongoDB template,
available on GitHub. If you want to learn more about this template, you can read
my article, but in a few words:
It's a simple CRUD Spring application that manages
a
persons collection, stored in MongoDB with a REST API.- Clone or download a zip of this repository.
If everything went as planned, you should now have a JAR file available in your
target folder
named java-spring-boot-mongodb-starter-1.0.0.jar.In Azure, you can now click on
Go to resource to access your new Azure Spring App.
Now, we can create our first microservice. Click on
Create App.
Insert a name for your application, select Java 17, and click
Create.
You can now access your new microservice.
In our Java project, our
application.properties file contains the following:This means that our Spring application will try to find a MongoDB URI in the
MONGODB_URI environment variable first,
and will default to mongodb://localhost if it doesn't exist.As we want to connect our microservice to our cluster in MongoDB Atlas, we have to set this environment variable
correctly.
- Create a new environment variable in your configuration.
Note: If you don't have a database user, it's time
to create one and use the login and password in your connection string.
MongoDB Atlas clusters only accept TCP connections from known IP addresses.
As our Spring application will try to connect to our MongoDB cluster, we need to add the IP address of our microservice
in the Atlas Network Access list.
- Retrieve the outbound IP address in the
Networkingtab of our Azure Spring App.
- Add this IP address to the network access list in Atlas.
We can now deploy our JAR file!
Click on the
Apps tab and Deploy app.
You'll see the instructions to deploy your application.
- We have to set our
Subscription ID:
- We can deploy!
If everything went well, you should see some logs happily telling you that the Spring app fired up successfully and
hooked up with our MongoDB Atlas cluster.
Finally, we need to assign an endpoint to our service to start discussing with the REST API.
Retrieve the endpoint to test the REST API. For me, it's:
You can create a
person using the following cURL command. Don't forget to change the endpoint.You can retrieve the persons from the MongoDB cluster in Atlas using the following
cURL command.Which should print something like this.
In our MongoDB Atlas cluster, we can confirm that the data was saved correctly.
And that's a wrap! You've smoothly navigated the realms of Azure Spring Apps and MongoDB, crafting a dynamic Spring Boot
application in the Azure Cloud. Your microservice is up, the REST API is ready, and MongoDB is seamlessly managing your
data.
Consider creating a free Atlas cluster and start exploring all the features
MongoDB Atlas has to offer.
Got questions or itching to share your success? Head over to
the MongoDB Community Forum – we're all ears and ready to help!
Cheers to your successful deployment, and here's to the exciting ventures ahead! Happy coding! 🚀
Rate this tutorial
Related
Tutorial
Introduction to Data Pagination With Quarkus and MongoDB: A Comprehensive Tutorial
Apr 25, 2024 | 7 min read
Tutorial
Seamless Media Storage: Integrating Azure Blob Storage and MongoDB with Spring Boot
Dec 15, 2023 | 9 min read