Search for a command to run...
How mid-sized companies migrate workloads to the cloud without blowing budgets. Strategy, sequencing, pitfalls, and what it actually costs.
Senior Freelancer & Technical Lead
Working as a Golang developer since 2020. Working as a mobile developer since 2013.
Focussed on architecture, testability and clean code. Open minded & product driven. Based in Rhede, available world-wide
No comments yet. Be the first to comment.
How to implement comprehensive software supply chain tracking using Open Component Model that captures dependencies, deployment artifacts, signatures, and version constraints across distributed systems.
A practical framework for evaluating and migrating from deprecated ingress controllers to Gateway API or Envoy Gateway, including risk assessment and zero-downtime migration patterns.
How modern software supply chains use component models to track dependencies, artifacts, and metadata across distributed systems, moving beyond traditional SBOMs to comprehensive delivery tracking.
How to implement comprehensive software supply chain tracking using the Open Component Model that captures dependencies, deployment artifacts, configurations, and runtime bindings across multi-repository environments.
Master React performance optimization through systematic profiling, efficient rendering patterns, and smart bundle splitting strategies for production applications. Learn practical techniques that actually move the performance needle.
Most cloud migrations in the midmarket fail not because of technology — they fail because of strategy.
The classic mistake: an IT services company promises to "move everything to the cloud," lifts VMs from an on-premise data center into AWS or Azure, and suddenly the company pays triple for the same performance. No auto-scaling, no automation, no modernization. Just a more expensive version of the status quo.
That's not a cloud project. That's a relocation with the wrong address.
Before a single server moves, three questions need answers:
1. What do we migrate — and in what order?
Not everything belongs in the cloud. An Oracle database with 15 years of stored procedures? Probably not first in line. A stateless API service with clean interfaces? Perfect starting point.
Sequencing decides whether you succeed or burn out. We use a simple assessment matrix:
2. Which migration pattern fits?
There's no one-size-fits-all. The common patterns from the AWS 7-R model:
For most midmarket companies, Replatform is the sweet spot: leverage managed services without rewriting everything.
3. How do we control risk and cost?
Cloud costs spiral when nobody's watching. According to the Flexera 2025 State of the Cloud Report, companies overspend by an average of 28%.
Our recommendations:
On-premise applications often communicate over local networks with sub-1ms latency. In the cloud, that jumps to 5-20ms. For some applications, that's irrelevant. For others, performance collapses.
Solution: Network assessment before migration. Identify latency-sensitive workloads and plan accordingly (same availability zone, VPC peering, or deliberately keep on-prem).
Once data leaves your data center, new rules apply. GDPR-compliant hosting location, data processing agreements, technical-organizational measures. For regulated industries (finance, healthcare), additional requirements kick in.
Solution: Data protection impact assessment before migration. Choose cloud region deliberately (EU-only). Encryption at-rest and in-transit as default.
The best cloud architecture is worthless if the team can't operate it. "We're migrating to the cloud" without training is like "we're switching to electric vehicles" without charging infrastructure.
Solution: Invest in cloud skills alongside the migration. AWS/Azure certifications, pair programming with experienced cloud engineers, runbooks for day-2 operations.
The question every CEO asks: "What does this cost me?"
A realistic estimate for a mid-sized company (50-500 employees):
| Phase | Duration | Investment |
| Assessment & Strategy | 2-4 weeks | Consulting + internal time |
| Pilot Migration (1-2 services) | 4-8 weeks | Engineering + cloud costs |
| Main Migration (waves) | 3-12 months | Engineering + cloud costs + parallel operation |
| Optimization & Stabilization | Ongoing | FinOps + monitoring |
Cloud infrastructure costs typically land at 60-80% of previous on-premise costs — when the migration is done right. With pure lift-and-shift, it can be 120-150%.
We run cloud migrations for midmarket companies. No slide decks — hands-on engineering:
No vendor lock-in, no black box. Everything transparent, everything documented, everything yours.