Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

There's no reason for anyone to preemptively colo their workload now in anticipation of higher prices.

You can't predict the future.

Just build your workloads to be cloud agnostic. If prices ever change, then you can move your workload wherever it makes sense at that time.

Locking yourself into a colo architecture is just as risky as locking yourself into AWS.



>Locking yourself into a colo architecture is just as risky as locking yourself into AWS

That's the game theoretical predicament: Colo's can take advantage of all this and increase their prices as well.

We just don't know how this whole thing will shake out. Given that uncertainty, I think you're proposing the only reasonable way forward for a little guy.

Be agnostic. Meliorate your market position by differentiating in some key area of your business where you can actually secure a competitive advantage.


You don’t have to use multiple clouds day to day, but forcing yourself to design your applications in cloud-agnostic ways makes it worthwhile.


We finally have a technical definition for what a professional software engineer is: someone who doesn't recommend "cloud-native" workloads.




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: