Note
Access to this page requires authorization. You can try signing in or changing directories.
Access to this page requires authorization. You can try changing directories.
Rebuilding components using serverless platforms enables you to build apps faster without managing infrastructure. In modernization scenarios, many use cases benefit from serverless workflows.
For example, if your application experiences unpredictable or highly variable workloads, serverless platforms can automatically scale to meet demand. You pay only for the compute resources you use, making this a cost-effective for handling bursts in traffic.
Serverless also suits rapid prototyping, development, and deployment. Services like Azure Functions and Azure Logic Apps abstract away the underlying infrastructure, allowing you to focus on writing code and defining workflows. Integration across services is smooth, enabling you to build complex, integrated solutions without managing the infrastructure. You can even build microservices and APIs quickly, creating lightweight, single-purpose functions that can be independently deployed and scaled.
Serverless considerations
Serverless platforms require a few special considerations:
- Security and compliance. Azure provides built-in security features, but you must also ensure that serverless solutions meet your security and compliance requirements. For example, use managed identities and secure environment variables.
- Costs. Serverless platforms follow a pay-as-you-go pricing model—you pay for the actual execution time of your functions. You need to consider the cost of applications used intermittently or infrequently.
- Performance. Serverless platforms suit applications that don’t have stringent latency and performance requirements. Serverless platforms can scale quickly, but cold start latency can affect infrequently used functions. For latency-sensitive applications, you should test whether serverless platforms can meet your performance criteria.
Rebuild enterprise messaging and routing apps with serverless platforms
A cloud-native approach to messaging and routing relies on an agile, resilient, scalable, and distributed infrastructure. Traditional messaging systems often struggle to provide the high scalability, real-time processing, and robust integration needed by today’s applications. These systems benefit from a modern event-driven architecture, including enterprise-grade messaging services and serverless computing.
In event-driven systems, applications and services that generate events are event producers. An event grid routes events at scale to appropriate handlers. A service bus helps ensure reliable delivery by managing the message queues and topics. Other services process messages and events and trigger workflows.
Choose a target
Azure provides a wide range of integration tools and capabilities that support this type of architecture. This guide focuses on the following services:
- Azure Service Bus for message queuing and topic-based publish/subscribe messaging.
- Azure Event Grid for event routing and handling real-time events.
- Azure Functions for process messages and events with an event-driven serverless compute platform.
- Azure Logic Apps for orchestrating workflows and integrating with other services.
Use case for enterprise messaging and routing
To show how Azure components work together in modern messaging and routing applications, consider a retail example. To maintain a physical inventory of products in near real-time, a retailer can design a smart distribution center like the one shown in the following diagram.
In this distribution center, Azure Event Grid, Azure Logic Apps, and Azure Service Bus track a retailer’s physical inventory in near real-time. Azure Functions transforms and maps data, using Service Bus as a message broker.
As part of the retailer’s supply chain, the smart distribution center supports fast order fulfillment. Azure Event Grid, Azure Logic Apps, and Azure Service Bus work together to expose the current status of the physical inventory in near real-time. Azure Kubernetes Service executes the order confirmation and tracking logic. The inventory data is also used to support order confirmation and tracking through a serverless event-driven architecture based on Azure Functions.
Serverless platforms are ideal for applications like this that respond to events, such as changes in data, user actions, or system events. You can use Azure Functions and Azure Event Grid to trigger functions based on events from various sources.
To further expand your integration platform, you can use these services with API-first design patterns. Building an API framework improves system reliability and supports future growth.
Next steps
Get started with the next cycle of activities and start to drive innovation during application modernization.