Introduction to the Fitness Store sample app
Note
The Basic, Standard, and Enterprise plans entered a retirement period on March 17, 2025. For more information, see the Azure Spring Apps retirement announcement.
The Standard consumption and dedicated plan entered a retirement period on September 30, 2024, with a complete shutdown by the end of March 2025. For more information, see Migrate Azure Spring Apps Standard consumption and dedicated plan to Azure Container Apps.
This article applies to: ❎ Basic/Standard ✅ Enterprise
This quickstart describes the fitness store sample application, which shows you how to deploy polyglot apps to an Azure Spring Apps Enterprise plan instance. You see how polyglot applications are built and deployed using Azure Spring Apps Enterprise plan capabilities. These capabilities include Tanzu Build Service, Service Discovery, externalized configuration with Application Configuration Service, application routing with Spring Cloud Gateway, logs, metrics, and distributed tracing.
The following diagram shows a common application architecture:
This architecture shows an application composed of smaller applications with a gateway, multiple databases, security services, monitoring, and automation.
This quickstart applies this architecture to a Fitness Store application. This application is composed of the following services split up by domain:
Four Java Spring Boot applications:
- Catalog Service contains an API for fetching available products.
- Payment Service validates and processes payments for users' orders.
- Identity Service provides reference to the authenticated user.
- Assist Service provides AI functionality to the fitness store.
One Python application:
- Cart Service manages users' items that have been selected for purchase.
One ASP.NET Core application:
- Order Service places orders to buy products that are in the users' carts.
One Node.js and static HTML application:
- Frontend is the shopping application that depends on the other services.