migrate-service-to-container

Migrating an existing backend service to a container module involves creating a directory under containers/<service-name> with config, src, and tests. You then transform imports to use shared libraries and loadConfig for standardized architecture.

You enforce multi-tenant isolation when refactoring services to containers by adding tenantId to all database queries. This tenant-aware query pattern ensures data segregation across tenants within the new container module.

The best way to replace hardcoded URLs when refactoring backend services is implementing config-driven ServiceClient usage. This approach centralizes endpoint management and standardizes service communication across container-based modules.

Yes, container migration requires event-driven communication wiring via EventPublisher for publishing and consuming events. This setup ensures decoupled, standardized event flow across the refactored backend architecture.

Update error handling when moving services to containers by replacing existing throw patterns with AppError. This enforces consistent error handling standards across all refactored backend services within the new module structure.

Setting up shared clients for containerized services requires dependencies on a shared client library and ModuleImplementationGuide. This provides shared DB and cache clients, enforcing standardized service initialization and configuration.