Summary

Congratulations! You deployed a Quarkus application to Azure Container Apps.

Your company wanted to deploy a Quarkus application to the cloud. You completed these steps:

1. Created a sample Quarkus application and ran and tested it locally.

2. Created an instance of Azure Database for PostgreSQL and configured your Quarkus application to access the database.

3. Containerized the Quarkus application.

4. Created an Azure Container Apps environment, deployed the Quarkus application container, and tested the application in the cloud.

5. Replaced the all-addresses PostgreSQL firewall rule with the Azure-services exception on the public database endpoint. The exception permits connection attempts from Azure resources, including the Quarkus application and resources in other customers' subscriptions. Database authentication is still required.

You're now confident that you can recommend running your Quarkus application in Container Apps.

Clean up resources

In this module, you created Azure resources in a resource group. If you don't need these resources, delete the resource group from the portal. Or run the following command:

az group delete \
    --name $AZ_RESOURCE_GROUP \
    --yes

This command might take a minute to run.

Additional resources

• Quarkus guides
• Azure Container Apps
• Azure Database for PostgreSQL documentation
• PostgreSQL firewall rules
• Hibernate ORM with Panache
• Azure for Java developers
• Compare Java application hosting options on Azure