5 ms·

We use Azure pretty seriously and overall, we really like it. We went with the MSFT stack due to some of our low level code to deal with printing. That being sa

by jspaur 14y ago

We use Azure pretty seriously and overall, we really like it. We went with the MSFT stack due to some of our low level code to deal with printing. That being said, it's had it's share of outages, but honestly no less than if we were racking and stacking our own machines. The most frustrating thing though (with any cloud provider really) is that if it goes down all you can do is sit and wait...atleast if its our fault we feel like we're in control.

niggler 14y ago
" it's had it's share of outages" Do you just sit on your hands when that happens? Do you have a failure plan?
- jspaur 14y ago
  We do have a failure plan (and ironically enough were actively working on improving storage resiliency, this just hit us before we were able to deploy it) That being said, there unfortunately is always a level 'sitting on hands' in events like this. If you're in dev you rely on your operations people (and vicea versa). You put your best people on it and continue to go on the best you can. All that being said, a fired rill just for the sake of doing something may cause more harm than good. If a rollover plan takes 2 hours (switch DNS, migrate data, test, stabilize, etc.) a) often times that'll take longer than the original issue requires to be resolved and b) you'll run into new issues in your new location (maybe environmental, maybe not)
- tarekayna 14y ago
  You seem to be asking more than one person about failure plans. What kind of a failure plan do you have in mind? For something as big as this (many azure services are completely down)
  - niggler 14y ago
    I generally worry about outsourcing a critical part of a business to one vendor without a plan for what happens if they go down. I'd ask the same question if people said they used AWS.
    - tarekayna 14y ago
      I agree to the general concept. I'm just curious about how you would handle it. Would you use AWS as backup to Azure and switch DNS when this happens? Anyone else is welcome to pitch in here, I'm new to native cloud applications and find myself just waiting in this case.

by jspaur 14y ago

niggler 14y ago

" it's had it's share of outages" Do you just sit on your hands when that happens? Do you have a failure plan?

jspaur 14y ago
We do have a failure plan (and ironically enough were actively working on improving storage resiliency, this just hit us before we were able to deploy it) That being said, there unfortunately is always a level 'sitting on hands' in events like this. If you're in dev you rely on your operations people (and vicea versa). You put your best people on it and continue to go on the best you can. All that being said, a fired rill just for the sake of doing something may cause more harm than good. If a rollover plan takes 2 hours (switch DNS, migrate data, test, stabilize, etc.) a) often times that'll take longer than the original issue requires to be resolved and b) you'll run into new issues in your new location (maybe environmental, maybe not)
tarekayna 14y ago
You seem to be asking more than one person about failure plans. What kind of a failure plan do you have in mind? For something as big as this (many azure services are completely down)
- niggler 14y ago
  I generally worry about outsourcing a critical part of a business to one vendor without a plan for what happens if they go down. I'd ask the same question if people said they used AWS.
  - tarekayna 14y ago
    I agree to the general concept. I'm just curious about how you would handle it. Would you use AWS as backup to Azure and switch DNS when this happens? Anyone else is welcome to pitch in here, I'm new to native cloud applications and find myself just waiting in this case.