Migrate Asset Manager repository

[timngmsft]

Create an assessment first. We will review the assessment.

[timngmsft]

App Modernization Assessment Summary

Target Azure Services: Azure Kubernetes Service, Azure App Service, Azure Container Apps

Overall Statistics

Total Applications: 1

Name: assets-manager-parent

• Mandatory: 7 issues
• Potential: 9 issues
• Optional: 5 issues

Severity Levels Explained:

• Mandatory: The issue has to be resolved for the migration to be successful.
• Potential: This issue may be blocking in some situations but not in others. These issues should be reviewed to determine whether a change is required or not.
• Optional: The issue discovered is real issue fixing which could improve the app after migration, however it is not blocking.

Applications Profile

Name: assets-manager-parent

• JDK Version: 21
• Frameworks: Spring Boot, Spring
• Languages: Java
• Build Tools: Maven

Key Findings:

• Mandatory Issues (36 locations):
  • AWS region configuration (2 locations found)
  • Local JDBC Calls (2 locations found)
  • AWS S3 dependency usage found (1 location found)
  • AWS S3 usage found (6 locations found)
  • No Dockerfile found (1 location found)
  • File system - Java NIO (14 locations found)
  • Spring Boot version is low (10 locations found)
• Potential Issues (11 locations):
  • Password found in configuration file (3 locations found)
  • PostgreSQL database found (5 locations found)
  • Java 2D library usage (1 location found)
  • Restricted configurations found (2 locations found)
• Optional Issues (10 locations):
  • Spring AMQP dependency found (1 location found)
  • RabbitMQ connection string, username or password found in configuration file (3 locations found)
  • Consider database reliability when migrating to Azure (1 location found)
  • Spring RabbitMQ usage found in code (4 locations found)
  • Localhost Usage (1 location found)

Next Steps

For comprehensive migration guidance and best practices, visit:

• GitHub Copilot App Modernization

[timngmsft]

Modernization Plan Created

Status: ✅ Plan creation succeeded

Branch: 010-migrate-rabbitmq-to-azure-service-bus

Plan Summary

Goal: Migrate the messaging layer from RabbitMQ to Azure Service Bus to leverage a fully managed cloud-native messaging service.

Total Tasks: 1

Task Breakdown:

1. Migrate from RabbitMQ to Azure Service Bus (Migration To Azure)
   • Replace RabbitMQ messaging implementation with Azure Service Bus
   • Update Maven dependencies from spring-boot-starter-amqp to Azure Service Bus Spring libraries
   • Replace RabbitMQ configuration with Azure Service Bus configuration
   • Update message producer code in Web module and message consumer code in Worker module
   • Migrate queue/topic configurations to Azure Service Bus entities
   • Update connection strings and authentication settings
   • Solution ID: amqp-rabbitmq-servicebus

Current vs Target Architecture

Current: Spring Boot 3.4.3 application using RabbitMQ with AMQP protocol for messaging between Web and Worker modules

Target: Same Spring Boot application migrated to use Azure Service Bus for managed messaging in Azure

---

The modernization plan has been created in branch 010-migrate-rabbitmq-to-azure-service-bus and is ready for review.