←back to thread

242 points panrobo | 1 comments | | HN request time: 0s | source
Show context
jsnell ◴[] No.42055205[source]
I don't know that 37Signals counts as a "major enterprise". Their Cloud exodus can't have been more than a few dozen servers, right?

Meanwhile AWS is growing at 20%/year, Azure at 33% and GCP at 35%. That doesn't seem compatible with any kind of major cloud repatriation trend.

replies(10): >>42055237 #>>42055401 #>>42055455 #>>42056381 #>>42057002 #>>42057897 #>>42059701 #>>42063493 #>>42074807 #>>42146570 #
PittleyDunkin ◴[] No.42057002[source]
You can have multiple trends at once. Veteran cloud users leaving, international business onboarding.
replies(2): >>42057850 #>>42058684 #
dhfuuvyvtt ◴[] No.42057850[source]
And then there's me: never left the datacenter in the first place.
replies(2): >>42057944 #>>42057946 #
hggigg ◴[] No.42057944[source]
Wise person. Wish we hadn't. Managed to multiply costs 8x (no joke).
replies(1): >>42060310 #
thrw42A8N ◴[] No.42060310[source]
No way that is true if you did it properly. Practically nobody has a workload where this could be true - and it's definitely not a workload smaller than several DCs.

It doesn't work out well if you just create some long lived EC2 instances and call it a day. But that's not really using a cloud, just a VPS - and that has indeed never been cheaper than having your own servers. You need to go cloud native if you want to save money.

replies(4): >>42060531 #>>42060677 #>>42061458 #>>42075253 #
1. randomcarbloke ◴[] No.42075253[source]
there is absolutely a crossover point at which it would've made more sense to stay put.

My organisation is feeling it now and while our cloud environment isn't fully optimised it has been designed with cost in mind.

Using opex to make up for otherwise unjustifiable capex is suitable only in the beginning or if you need the latest servers every six (or whatever) months