Quarkus - Azure Functions (Serverless) with Resteasy, Undertow, or Vert.x Web

The quarkus-azure-functions-http extension allows you to write microservices with Resteasy (JAX-RS),Undertow (servlet), or Vert.x Web and make these microservices deployable to the Azure Functions runtime.

One azure function deployment can represent any number of JAX-RS, servlet, or Vert.x Web endpoints.

Prerequisites

To complete this guide, you need:

Solution

This guide walks you through running a Maven Archetype to generate a sample project that contains three http endpointswritten with JAX-RS APIs, Servlet APIs, and Vert.x Web APIs. After building, you will then be able to deployto Azure.

Creating the Maven Deployment Project

Create the azure maven project for your Quarkus application using our Maven Archetype.

  1. mvn archetype:generate \
  2.     -DarchetypeGroupId=io.quarkus \
  3.     -DarchetypeArtifactId=quarkus-azure-functions-http-archetype \
  4.     -DarchetypeVersion=1.0.0.CR1

Running this command will run maven in interactive mode and it will ask you to fill in some build properties:

  • groupId - The maven groupId of this generated project. Type in org.acme.

  • artifactId - The maven artifactId of this generated project. Type in quarkus-demo

  • version - Version of this generated project.

  • package - defaults to groupId

  • appName - Use the default value. This is the application name in Azure. It must be a unique subdomain name under *.azurewebsites.net. Otherwise deploying to Azure will fail.

  • appRegion - Defaults to westus. Dependent on your azure region.

  • function - Use the default which is quarkus. Name of your azure function. Can be anything you want.

  • resourceGroup - Use the default value. Any value is fine though.

The values above are defined as properties in the generated pom.xml file.

Login to Azure

If you don’t login to Azure you won’t be able to deploy.

  1. az login

Build and Deploy to Azure

The pom.xml you generated in the previous step pulls in the azure-functions-maven-plugin. Running maven installgenerates config files and a staging directory required by the azure-functions-maven-plugin. Here’show to execute it.

  1. mvn clean install azure-functions:deploy

If you haven’t already created your function up at azure, the will build an uber-jar, package it, create the functionat Azure, and deploy it.

If deployment is a success, the azure plugin will tell you the base URL to access your function.

i.e.

  1. Successfully deployed the artifact to https://quarkus-demo-123451234.azurewebsites.net

The URL to access the service would be

https://{appName}.azurewebsites.net/api/hellohttps://{appName}.azurewebsites.net/api/servlet/hellohttps://{appName}.azurewebsites.net/api/vertx/hello

Extension maven dependencies

The sample project includes the Resteasy, Undertow, and Vert.x Web extensions. If you are only using one of thoseAPIs (i.e. jax-rs only), respectively remove the maven dependency quarkus-resteasy, quarkus-undertow, and/orquarkus-vertx-web.

You must include the quarkus-azure-functions-http extension as this is a generic bridge between the Azure Functionsruntime and the HTTP framework you are writing your microservices in.

Azure Deployment Descriptors

Templates for Azure Functions deployment descriptors (host.json, function.json) are withinthe azure-config directory. Edit them as you need to. Rerun the build when you are ready.

NOTE: If you change the function.json path attribute or if you add a routePrefix,your jax-rs endpoints won’t route correctly. See Configuring Root Paths for more information.

Configuring Root Paths

The default route prefix for an Azure Function is /api. All of your JAX-RS, Servlet, and Vert.x Web endpoints mustexplicitly take this into account.

If you modify the path or add a routePrefix within the azure-config/function.jsondeployment descriptor, your code must also reflect any prefixes you specify for your path.