Skip to content
Beta

Replatform to STACKIT: Spring Boot and PostgreSQL Overview

Last updated on

Stackit LogoStackit Logo
STACKIT

Replatform to STACKIT: Spring Boot and PostgreSQL Overview

Plan the Spring Boot platform change to SKE and PostgreSQL Flex: discovery, architecture, landing-zone readiness, migration gates, handoff, and optimization.

PLAN

Spring Boot Replatform Journey

Place the platform change within the complete Migration Framework: assess the workload, design SKE and PostgreSQL Flex, prepare the landing zone, migrate with explicit data gates, and stabilize before optimization. The application JAR stays the same; the runtime and database operating models change.

STACKIT Cloud Migration Framework Journey across the four phases Assess, Design and Mobilize, Migrate, and Run with their key modules. Assess PHASE 1 Assess Design & mobilize PHASE 2 Design & mobilize Migrate PHASE 3 Migrate Run PHASE 4 Run PLANNING Discovery Discovery Map apps and dependencies. Design Design Define target patterns. Migration plan Migration plan Sequence waves for delivery. Rapid discovery Rapid discovery Inventory workloads to create an early scope and cost baseline. TCO report TCO report Model migration economics to support investment and planning decisions. Readiness assessment Readiness assessment Assess technology and organization gaps before detailed design starts. Deepdive workshop Deepdive workshop Explore STACKIT services and platform options for target design. Briefings & workshops Briefings & workshops Align stakeholders on goals, scope, and migration expectations. Business case Business case Compare value, effort, and investment per application. Enablement ENABLEMENT Center of Excellence Trainings & Learning Paths Documentation & Reference Landing zone Landing zone Establish the secure platform base for migrated workloads. Security & compliance Security & compliance Define security and compliance controls for migration and operations. Target operating model Target operating model Define roles, processes, and ownership for target operations. Migration factory setup Migration factory setup Prepare teams, tools, and runbooks for scalable migration execution. Migrate MIGRATE Relocate Relocate Rehost Rehost Replatform Replatform Optimize Optimize Improve sizing, performance, and cost after cutover. Repurchase Repurchase Evaluate SaaS options when replacement delivers better value. Refactor Refactor Restructure strategic workloads for cloud- native scalability and agility. Operating model handover Operating model handover TOM validation and ownership transfer Hypercare Hypercare Post-cutover stabilization bridge. Operate Operate Steady-state cloud operations. Support Support Manage incidents and service requests across support responsibilities. Customer Success Customer Success Track adoption, outcomes, and value realization with stakeholders.
STACKIT Migration Framework from Assess through Design and Mobilize and Migrate to Run
PLAN

Rapid Discovery

Establish an initial workload baseline for the Spring Boot VM, PostgreSQL data, dependencies, and capacity. Qualify migration intent and identify the unknowns that detailed Discovery must resolve before a platform decision.

AssessRapid discoveryOverview In 4 trails
Rapid discovery process Input data is processed through rapid discovery tooling to produce decision-ready outputs for early migration choices. Input dataCMDB & inventory exportsAsset lists, hosts, base platform factsHypervisor & cloud reportsUsage, footprint, and utilization signalsPlatform listsKubernetes, database, and OS baselinesRapid discovery toolingIngest & normalize datasetsStandardize source records and schemaClassify & aggregate assetsConsolidate by technology and quantityApply assumptionsConfidence levels and growth factorsOutput informationConsolidated asset baselineFact base for scope and planningInitial STACKIT sizingFirst capacity assumptionsPrice indication & TCO corridorEarly cost orientation for decisions
Rapid Discovery process from source collection to an initial migration baseline

Rapid Discovery provides a fast, automated baseline of the current environment across on-premises and cloud landscapes. The focus is on quantifying the existing IT portfolio in a short time window, so teams can make early migration and commercial decisions with confidence.

At this stage, quantity and distribution matter more than deep application relationships.

STEP

Discovery

Confirm Java and PostgreSQL compatibility, state handling, scheduled writers, schema dependencies, data volume and change rate, downtime tolerance, recovery objectives, and representative demand. Validate those inputs with the application and database owners before selecting the target.

Design and mobilizeDiscoveryOverview In 4 trails
Discovery source-to-decision flow Discovery separates technical and human-driven inputs, runs technical-first and human-enriched analyses, and hands over both insight streams to follow-on modules. Discovery inputsTechnical and automated discoveryInfrastructure inventoryCMDB, VM, database, middleware, storageRuntime and utilization dataCPU, memory, I/O, network and seasonalityIntegration and flow signalsNetwork paths, APIs, identity, data movementAssessment-driven human inputSecurity and compliance contextData classes, controls, audit requirementsOwner and business inputCriticality, release windows, lifecycle plansDiscovery analysis toolingTechnical-first analysesNormalize and correlateUnify records and technical identitiesDependency mappingInfer communication and couplingUtilization and sizing analysisEstimate baseline demand corridorsPreliminary segmentationCluster by stack and environmentHuman-driven analyses (application owner input)Criticality and risk calibrationValidate business impact and constraintsWave feasibility and sequencingReconcile dependencies with release windowsAssumption and gap registerTrack open points and confidenceHandover outputsTool-derived outputsDesignTarget architecture options and sizing factsLanding zonePlatform guardrails and account structure needsMigration planWave backlog, sequencing, and cutover windowsAssessment-validated outputsSecurity and complianceControl needs, data classes, remediation pointsOperating modelRole model, ownership boundaries, process impactBusiness caseValue/risk profile and modernization priorities
Discovery analysis combining technical measurements and application-owner evidence

Discovery is one of the first and most critical modules in the Design and Mobilize phase. It refines Rapid Discovery results and adds the depth needed to make architecture and migration-wave decisions with confidence.

The primary objective is to establish a realistic, evidence-based understanding of the current IT landscape, business priorities, and organizational readiness before detailed target design and migration planning are finalized.

LIFT

Replatform Strategy and Tools

Confirm the two deliberate substitutions: a VM service becomes a Kubernetes Deployment, and VM-local PostgreSQL becomes PostgreSQL Flex. Preserve the Spring Music JAR and business behavior; this is Replatform rather than VM Rehost or application Refactor.

Design and mobilizeDesignReplatform In 2 trails
R-strategy migration method Decision flow from discovery to production with the seven R-strategies: Relocate, Rehost, Replatform, Repurchase, Refactor, Retain, and Retire. R-strategy migration methodFrom discovery and path selection through the seven R-strategies to validation, transition, and production.DiscoveryDiscoveryAssess / prioritizeAssess / prioritizeDetermine migration pathDetermine migration pathValidationValidationTransitionTransitionProductionProductionRelocateRelocate(move VM)Define Landing ZoneDefine Landing ZoneUse migration toolsUse migration toolsAUTOMATEMANUALInstallInstallConfigConfigDeployDeployValidation & handoverRehostingRehosting(move application)Define Landing ZoneDefine Landing ZoneUse migration toolsUse migration toolsAUTOMATEMANUALInstallInstallConfigConfigDeployDeployReplatformingReplatforming(lift and reshape)Define Landing ZoneDefine Landing ZoneMap Target PlatformMap Target PlatformAdapt Platform StackAdapt Platform StackRepurchasingRepurchasing(replace, drop and shop)Purchase COTS/SaaS and licensingPurchase COTS/SaaS and licensingMigrate business processMigrate business processRefactoringRefactoring(re-architecting applications)Redesign application/ infrastructure architectureRedesign application/ infrastructure architectureApp code developmentApp code developmentFull ALM/SDLCFull ALM/SDLCIntegrationIntegrationRetain/moveRetain/movekeep for now or move laterRetire/decommissionRetire/decommissionLanding zone foundationLanding zone foundationShared platform base for all paths
R-strategy method placing Replatform between Rehost and Refactor

Replatform keeps core application behavior but changes selected platform components to gain operational or economic benefits. It sits between Rehost and Refactor in change intensity.

STEP

Automate Platform and Workload

Use versioned Terraform for infrastructure and Kubernetes resources, Helm for Envoy Gateway and routes, and a separate approved script for data migration. Keep provisioning and data replacement independently reviewable; this target does not require Ansible host configuration.

Design and mobilizeLanding zonesAutomation (IaC) In 3 trails
  • STACKIT API: Use the API as the foundational control surface for platform automation and integration patterns. Documentation
  • Terraform Provider: Use the official provider for declarative infrastructure provisioning and lifecycle control. Documentation
  • OpenTofu Provider: Use OpenTofu with the STACKIT provider as an open IaC option with comparable declarative workflows. Documentation
  • Pulumi: Use Pulumi when teams prefer general-purpose languages for infrastructure automation. Documentation
  • Ansible: Use Ansible primarily for post-provisioning configuration and operational tasks. In a combined model, Terraform/OpenTofu provision infrastructure while Ansible applies OS and middleware configuration.
  • STACKIT CLI: Standardize CLI-based operations for scripting, troubleshooting, and repeatable operational run tasks. Documentation
  • SDKs (Go, Python, Java): Use SDKs for custom automation and service integrations where IaC abstractions are not sufficient. Go SDK , Python SDK , Java SDK .
  • STACKIT Git: Use Git as the source of truth for IaC modules, policies, and delivery workflows. Documentation
  • CI/CD Pipeline: Use pipelines for validation, policy checks, controlled promotion, and auditable releases. Documentation
  • Container Registry: Use a central registry for versioned build artifacts and deployment consistency across environments. Documentation
OPS

Target Runtime Architecture

Source VMApproved dump + manifestApplication clientsSTACKIT Application ProjectSpring Music JAR + systemdSelf-managed PostgreSQLSTACKIT DNSSKE: single-worker referencePostgreSQL FlexObservability + GrafanaEnvoy Gateway + HTTPRoutesClusterIP ServiceSame JAR on Java 11Boot 2 adapter + PG exporterTemporary migration clientManaged ExternalDNSspringmusicspringmusic_rehearsal local SQL watch route hostnamesJDBC / TLSrehearse / prove backupapproved cutover / rollbackdatabase metrics / TLSpublish Gateway addressscrape via Gateway 9090 / 9187freeze / export / verifyprotected transfer via kubectlresolve hostnameHTTP baseline; HTTPS optional
AUTO

Database Migration

Design the database move independently of runtime provisioning. Define source freeze, a consistent dump and manifest, isolated rehearsal, a proven target backup, transactional restore, and the rollback deadline. Traffic switching and source failback remain explicit operator decisions.

Design and mobilizeDesignReplatform In 2 trails
End-to-End Migration Wave Flow Four sequential stages lead from wave approval through preparation and cutover to stabilization and handover. Every wave follows the same controlled factory flow. Secure scope and baseline, execute migration, prove acceptance, and hand over safely to operations. 1 APPROVE Scope and baseline Window, rollback, and ownership Freeze versions and dependencies 2 PREPARE Readiness and R-path Validate source and target Run playbook by archetype 3 CUT OVER Cutover and acceptance Route traffic to STACKIT safely Validate tech, function, operations 4 STABILIZE Learn and hand over Resolve findings in short loops Hand over to Optimize and Operate Traceable wave completion: accepted, stabilized, and fully handed over
Migration-wave control points from readiness through cutover, validation, and handover

For stateful workloads, define source and target data platform responsibilities before runtime cutover.

  • Source data ownership: Clarify who owns dump/export run and consistency checks.
  • Target data ownership: Clarify who owns managed database provisioning, access controls, and backup baseline.
  • Migration sequencing: Separate schema/data move from runtime switch and validate each gate independently.
  • Temporary access controls: Plan temporary data migration access and explicit rollback/removal checkpoints.
BASE

Landing Zone

Establish governance, identity, security, network, cost controls, and automation before the target depends on them. Confirm project permissions, operator access, DNS delegation, SKE capacity, database access boundaries, and protected Terraform state.

Design and mobilizeLanding zonesOverview In 6 trails
Landing zone core components Six building blocks of a secure landing zone. Landing zone core componentsThe six building blocks of a secure platform foundation on STACKIT.Account GovernanceAccount GovernanceHow do I structure my projects?Identity & Access ManagementIdentity & Access ManagementWho can do what on the platform?Security & ComplianceSecurity & ComplianceHow do I monitor and protect?Network ArchitectureNetwork ArchitectureHow are components securely connected?Cost Management and ControlCost Management and ControlHow do I keep spending in control?Automation (IaC)Automation (IaC)How is everything delivered and managed?
Six core components of a governed STACKIT landing zone

A landing zone is the structured cloud foundation that defines how your organization operates on STACKIT from day 1. It combines governance, identity, security, network design, cost controls, and automation into one coherent baseline.

Without this foundation, migration waves typically stall due to missing approvals, inconsistent controls, and repeated platform decisions.

Accelerate the Foundation as Code

Use the Landing Zone Accelerator where appropriate for the governed project and platform foundation. Keep responsibility separate: the application team owns the SKE workload, data migration, Gateway, telemetry, and workload recovery.

Landing Zone Accelerator separating platform foundation and application workload responsibilities
Landing Zone Accelerator separating platform foundation and application workload responsibilities
LIVE

Migration Framework

Enter the migration wave with an approved target design, a ready Application Landing Zone, a tested runbook, and assigned decision owners. Follow readiness, migration, cutover, validation, stabilization, and handover as one controlled flow.

MigrateMigrateOverview In 4 trails
  1. Confirm wave scope, cutover window, rollback criteria, and runbook ownership.
  2. Freeze wave baseline (application version, dependencies, data scope, and interface contracts).
  3. Run pre-migration technical readiness checks in source and target environments.
  4. Run migration runbook steps per workload archetype and R-strategy path.
  5. Perform cutover and route traffic to the STACKIT target according to the wave plan.
  6. Validate technical, functional, and operational acceptance criteria.
  7. Stabilize incidents and known defects in short feedback loops.
  8. Hand over stabilized workloads to Optimize and Operate.
SAFE

Migration Decisions and Gates

  • Ready to migrate: approve the target design, access boundaries, downtime, responsibilities, and measurable acceptance criteria before opening the window.
  • Ready to cut over: freeze source writes and require a consistent final dump with matching, recent rehearsal evidence. Infrastructure readiness alone does not authorize replacing data.
  • Protected execution: exclude competing writers and reconcilers, prove the pre-cutover target backup, and validate the transactional restore before restarting the workload.
  • Accept or recover: require matching data, successful business journeys, working client traffic, and actual telemetry. Decide rollback before the deadline; source failback and post-cutover write reconciliation remain separate decisions.
  • Ready for operations: transfer evidence and recovery ownership, stabilize the workload, and resume automation deliberately. Capacity and HPA experiments belong to a later change window.

These gates explain the control model. The following sections provide the executable procedure and evidence requirements for the technical walkthrough.

GOAL

Accept and Hand Over to Operations

Transfer configuration, acceptance evidence, dashboards, incident ownership, and source-retention decisions.

Transfer the reviewed configuration revision, workload and Gateway inventory, source manifest, migration journal, backup locations, acceptance results, dashboard URL, and rollback decision. Keep credentials out of the handover document; reference the approved secret store instead.

Agree an initial 24-72 hour stabilization window appropriate to the workload. Assign named incident and database recovery owners, confirm retention and restore procedures, and test alert delivery before relying on it. Flex backups complement migration dumps; a verified dump rollback is not proof of managed-service recovery.

Exit stabilization only with sustained business health, complete telemetry, no unresolved critical issues, and operations sign-off. Resume paused automation deliberately. Keep source data and protected evidence until the agreed retention and reconciliation gates permit decommissioning. Begin HPA and capacity experiments only after stabilization, in a separate change window.

GOAL

Stabilize and Optimize

Return to the Migration Framework's Optimize loop: collect representative operating evidence, identify the limiting layer, implement one controlled change, and validate reliability, performance, and cost before keeping it.

MigrateOptimizeOverview In 7 trails

Optimize starts when workloads run on STACKIT and real operating data is available. The module converts post-cutover observations into measurable improvements for performance, stability, and cost efficiency.

Optimize is not a one-time task. It is an iterative cycle that can overlap with early stabilization and post-cutover care.

Many right-sizing and tuning decisions are only reliable under real load patterns. After cutover, teams can use production telemetry to separate assumptions from actual behavior.

  1. Collect runtime evidence: utilization, latency, error rates, throughput, and cost drivers.
  2. Identify bottlenecks and waste patterns at workload, platform, and data layers.
  3. Prioritize actions by business impact, risk reduction, and FinOps effect.
  4. Implement tuning changes in controlled increments.
  5. Validate outcomes against SLO, reliability, and cost targets.
  6. Feed lessons learned into future migration waves and operating standards.
  • Rightsizing: Align compute, storage, and network capacity with actual demand profiles.
  • Performance tuning: Improve latency and throughput through configuration, scaling, and architecture adjustments.
  • Reliability hardening: Reduce incident frequency through better resilience, observability, and failure handling.
  • FinOps controls: Improve cost transparency, remove waste, and optimize run-rate efficiency.
STACKIT LogoSTACKIT Logo
Optimize Replatform Spring Boot on Kubernetes with Rightsizing and Pod Scaling STACKIT · Runbook Open asset ↗

Open grafana_dashboard_url or the SCF Replatform folder. Terraform manages eight panels.

Replatform Grafana dashboard showing cluster CPU and memory, one Spring Boot pod, application requests, and PostgreSQL Flex metrics over one hour

Snapshot from the reference deployment on September 25, 2026, 14:41-15:41 UTC. This is one hour of low-load test operation, not a representative production sizing baseline. Read application activity alongside database availability and pressure before selecting an optimization candidate; the panel interpretations below explain the limits of these signals.

Verify both scrape jobs have actual up=1 samples before interpreting the dashboard. Some cluster panels include fallback values, so a rendered zero is not evidence of zero consumption. Scope queries to the intended cluster and database when a datasource contains multiple workloads. Use additional telemetry and business tests for latency percentiles, errors, and recovery objectives.

Trail historyActive 2 of the last 12 weeksLWUpdatedNo updates · 1 bar = 1 week i
Maintainer
LWLukas WeberrußHead of STACKIT Cloud Migration Framework · STACKITOwnerActive 12 of the last 12 weeks · 58 updatesSTACKITwww.linkedin.com/in/lukas-weberruß-a360b081Contributed in STACKIT
Show full history (1 more)