11–20 of 67 posts
I can recommend trying AppHarbor - we're striving to deliver a better .NET and Windows cloud platform. Feel free to shoot me an email (rs@appharbor.com) if there's anything I can help with.
It seems like a prudent step to take.
Maybe a noobish question, but in the future, is there anything other than need for preparation, that prevents you from having a backup spun up on say AWS or another service provider? It seems like a prudent step to take.
No response? You suck.
God says...
9:33 And Moses went out of the city from Pharaoh, and spread abroad his hands unto the LORD: and the thunders and hail ceased, and the rain was not poured upon the earth.
9:34 And when Pharaoh saw that the rain and the hail and the thunders were ceased, he sinned yet more, and hardened his heart, he and his servants.
9:35 And the heart of Pharaoh was hardened, neither would he let the children of Israel go; as the LORD had spoken by Moses.
10:1 And the LORD said unto Moses, Go in unto Pharaoh: for I have hardened his heart, and the heart of his servants, that I might shew these my signs before him: 10:2 And that thou mayest tell in the ears of thy son, and of thy son's son, what things I have wrought in Egypt, and my signs which I have done among them; that ye may know how that I am the LORD.
It's a chance we take when we deploy to the cloud, and services like Heroku only compound it because that's an additional point of failure. I'm not sure a giant "it's their fault" finger point is the best way to handle a problem, but I assume they feel pretty powerless, so finger pointing is an option.
Good luck resuming operations. Hopefully you won't loose too many customers.
This extends to those services that blames AWS as well. It's not a good habit, and customers (like we saw with netflix) don't care -- all they know is that their service is down.
When can we move beyond blaming a cloud service and just owning up to the decision? Soluto chose to use Azure and knew they were taking a risk. It's their fault for choosing to use Azure, and unless they signed for a 100.000000000% uptime guarantee (which I'm sure they didn't, given no one would give such a guarantee) they have to own up to any faults. This extends to those services that blames AWS as well. It's not…
When can we move beyond blaming a cloud service and just owning up to the decision? Soluto chose to use Azure and knew they were taking a risk. It's their fault for choosing to use Azure, and unless they signed for a 100.000000000% uptime guarantee (which I'm sure they didn't, given no one would give such a guarantee) they have to own up to any faults. This extends to those services that blames AWS as well. It's not…
No one's "blaming" anyone. The expectancy is that cloud providers work their asses off to fix stuff that gets broken, which is the case.