Menu

Post image 1
Post image 2
1 / 2
0

The lift n' shift

DEV Community·Mariano Barcia·25 days ago
#3hJMLxIP
#quarkus#java#tpf#serverless#marta#everything
Reading 0:00
15s threshold

This is the continuation of "The script that refused to stay small" . The conversation had already been happening for months: three data centers, rising costs, aging hardware, and a growing sense that the whole setup was one incident away from becoming a liability. The decision came quickly after the "kalima" event: everything had to move. What followed was not elegant, as the platform team scrambled to pull off a lift & shift: hypervisor VMs mapped 1:1 into cloud instances network rules replicated (and occasionally guessed) storage reattached, sometimes awkwardly timelines optimistic, then revised, then ignored Most applications... just came along for the ride whilst Marta watched all of this unfold. Her service was, technically, just another VM in the inventory. It could have been copied over, like everything else, but the lift and shift was rushed and was accumulating tech debt almost by definition. So she made a different call.…

Continue reading — create a free account

Join HashtagPLUS to read full articles, follow hashtags, vote, and join the conversation.

Read More