Architecture target state
Define decomposition boundaries, service interactions, and reliability patterns.
Refactor
Last updated on
Understanding Refactor
Section titled “Understanding Refactor”Refactor redesigns parts of the application and delivery model for cloud-native operation. It is the most change-intensive path and should be applied selectively to strategic workloads.
When Refactor Is a Good Fit
Section titled “When Refactor Is a Good Fit”- Strategic differentiation depends on faster product and feature delivery.
- Current architecture limits resilience or scalability beyond acceptable risk.
- Legacy debt blocks innovation and causes recurring operational instability.
- Long-term value outweighs near-term migration effort and governance complexity.
Design Considerations in STACKIT Context
Section titled “Design Considerations in STACKIT Context”Engineering and delivery model
Align CI/CD, testing strategy, and release governance with the new architecture.
Data and integration refactoring
Plan schema transitions, interface versioning, and coexistence strategy.
Operational model
Define observability, SRE responsibilities, and incident response for the new runtime.
Recommended Design Flow
Section titled “Recommended Design Flow”- Baseline technical debt and business constraints.
- Define target architecture slices and migration increments.
- Design transition states and compatibility contracts.
- Validate reliability, security, and performance requirements.
- Approve phased delivery roadmap with business checkpoints.
Required Outputs
Section titled “Required Outputs”Shared outputs across all migration paths
Section titled “Shared outputs across all migration paths”- Approved design decision record with scope, assumptions, and governance sign-off.
- Validation evidence package for security, compliance, and operational readiness.
- Strategy-specific migration runbook draft from the Design phase.
- Handover package for Migration Factory Setup and wave planning.
Refactor-specific outputs
Section titled “Refactor-specific outputs”- Refactor decision record and value hypothesis.
- Target architecture with transition states.
- Delivery roadmap and engineering controls.
- Data/integration transition design.
- Runbook and operations readiness package.
Diagram Step Reference
Section titled “Diagram Step Reference”Redesign application/infrastructure architecture
Section titled “Redesign application/infrastructure architecture”Define the redesigned architecture baseline and transition boundaries. Describe domain decomposition, target runtime decisions, and interim coexistence states so refactor increments can be delivered without destabilizing dependent systems.
App code development
Section titled “App code development”Define implementation scope and change packaging for the redesigned architecture. Define increment boundaries, test strategy, and release criteria per slice so code changes remain deployable within migration wave constraints.
Full ALM/SDLC
Section titled “Full ALM/SDLC”Define delivery pipeline, quality gates, and release governance model. Align branch strategy, automated checks, and approval gates with security and compliance evidence requirements before production cutover.
Integration
Section titled “Integration”Define integration transition, compatibility handling, and final handover controls. Specify API contract versioning, rollback behavior, and cross-team cutover communication to reduce integration regression risk.