Files
demo-b-5/docs/migration-plan.md
demo-bot f94f96fba2 feat: modernize application — source, platform artifacts, CI/CD
- chore: ingest source code

113 files from https://github.com/spring-projects/spring-petclinic
- feat: add platform deployment artifacts
- feat: add CI/CD workflow automation
2026-10-16 16:48:21 +00:00

43 lines
1.6 KiB
Markdown

# Modernization Plan for demo-b-5
## Application Type
Java Application
## Selected Modernization Strategy
- **Migration Approach**: containerize-optimize
- **Target Platform**: orchestrator
- **Observability**: ENABLED (Prometheus metrics, health checks, tracing)
- **Security Scanning**: ENABLED (Trivy vulnerability scanning)
## Discovery Summary
### Discovery Report
#### Application Overview
The application appears to be a Java-based project using the Spring framework. It includes both Maven and Gradle build files, suggesting compatibility with both build systems. The presence of Spring Boot dependencies and API endpoints indicates that this is a web application, likely following the MVC (Model-View-Controller) architecture.
#### Technology Stack
- **Language:** Java
- **Framework:** Spring Boot
- **Build Tools:** Maven and Gradle
- *...
## Generated Artifacts
1. **Dockerfile**: Optimized with health checks and metrics endpoints
2. **score.yaml**: Platform intent with service ports and DNS resource
3. **CI Workflow**: Automated build/push to ACR with Trivy security scanning
## Next Steps
1. Review and customize generated artifacts
2. Test container build and run
3. Deploy to development environment using score.yaml
4. Validate application functionality
5. Promote to staging/production via Humanitec
## Migration Strategy Details
### Containerize Optimize
Add cloud-native patterns: health checks, metrics, optimized base images.
### Platform: orchestrator
score.yaml optimized for Azure Container Apps with managed scaling and Azure-specific configuration.