Azure Functions is a serverless computing service that allows you to run code without managing infrastructure. It is equivalent to AWS Lambda Functions and extends the concept of Platform as a Service (PaaS) by abstracting infrastructure details and facilitating auto-scaling.
Key benefits of Azure Functions include:
- Automatic scaling
- Reduction of time to market
- Agile deployment
- Pay-per-use
As stated by Gartner, "Serverless architectures enable developers to focus on what they should be doing –writing code and optimizing application design– making way for business agility and digital experimentation".
Azure Functions is ideal for scenarios where you want data processing to react to events and pay only for the resources consumed. It is not suitable for long-running batch procedures.
Data processing can be triggered by various events, including:
- Timer triggers (cron jobs)
- Queue triggers
- Service Bus triggers
- HTTP triggers
- CosmosDB triggers
- Blob Storage triggers
- Event Grid triggers
To implement Azure Functions in GeneXus, refer to the following guides:
| |
Windows |
Linux |
| Net Core 3.1 (In-process execution model) |
Yes |
Yes |
| Net 5 (Isolated Worker model) |
Yes |
No |
| Net 6 (Isolated Worker model) |
Yes |
Yes |
| Net 8 (Isolated Worker model) |
Yes |
Yes |
| Java 8, 11, 17 |
Yes |
Yes |
To deploy your application to Azure Functions, follow the steps outlined in HowTo: Deploy as Azure Functions.
HowTo: Troubleshoot Azure functions
HowTo: Monitor Azure Functions