5 ms·

Some good points, not all correct.. but we're seeing some major sites out right now that, if I were invested in them at the VC level, I'd be looking at the CTO

Some good points, not all correct.. but we're seeing some major sites out right now that, if I were invested in them at the VC level, I'd be looking at the CTO to justify their decisions for using Heroku/AWS without at least a non-cloud backup. I may even be looking to fire someone. >> Kudos, you also worry about hardware all of the time Patently untrue. I haven't thought about hardware once in three years because I have an admin whom I've personally trained that worries for me. He knows how to scale hardware and software because I've showed him how to do it properly, and he has earned my trust. I get to spend every minute of every work hour coding solutions. If you're a business owner and YOU still worry about hardware, then you need to fire your admins and hire rockstar-level admins. My admin spends no more than 2 hours a day on colo management because he does it the right way. >> Congrats. Inevitably, a UPS will overload, a switch will die & you'll eat some downtime too. It happens -- build redundancy into your application / service to ensure that thy facility is irrelevant when the time comes. I use external DNS to handle dynamic re-routing to an alternate colo should connectivity or power to this one fail. Even with this setup, it would cost more than 2 times as much to do what I do on the cloud, even if I used EC2 committed instances. What's important is NOT to have NO downtime. What's important is to be PERCEIVED to have no downtime. Customers should never see downtime from you. It should be transparent to them, giving you a 100% uptime public personna.

davidandgoliath 14y ago
>> Some good points, not all correct.. but we're seeing some major sites out right now that, if I were invested in them at the VC level, I'd be looking at the CTO to justify their decisions for using Heroku/AWS without at least a non-cloud backup. I may even be looking to fire someone. And I'd be asking why they don't have redundancy. >> I haven't thought about hardware once in three years because I have an admin whom I've personally trained that worries for me. He knows how to scale hardware and software because I've showed him how to do it properly, and he has earned my trust. But not everyone using heroku / aws / etc. have this same guy, trained by yourself, available. Thus, they use a service that makes that aspect of it invisible to them. Downtime still happens irregardless. >> I get to spend every minute of every work hour coding solutions. If you're a business owner and YOU still worry about hardware, then you need to fire your admins and hire rockstar-level admins. My admin spends no more than 2 hours a day on colo management because he does it the right way. Admittedly, I don't worry about it as much as I'd let on -- but there's still some aspects that I dig into by choice to make certain everything is in good working order, and that there are ample replacements on-site to mitigate the 'worst case scenario'. As a CEO, I fight on behalf of my users & clients daily, even if that means wasting mental bandwidth on what might be defined as someone elses' job. In a perfect world none of us would have to worry about hardware or downtime. Heroku is responsible for Heroku, and AWS is responsible for AWS -- and every user thereof is responsible for themselves and their operations. Colo. might be the answer for some of them, but it's not a perfect world either.
- PythonDeveloper 14y ago
  Well said.

davidandgoliath 14y ago

>> Some good points, not all correct.. but we're seeing some major sites out right now that, if I were invested in them at the VC level, I'd be looking at the CTO to justify their decisions for using Heroku/AWS without at least a non-cloud backup. I may even be looking to fire someone. And I'd be asking why they don't have redundancy. >> I haven't thought about hardware once in three years because I have an admin whom I've personally trained that worries for me. He knows how to scale hardware and software because I've showed him how to do it properly, and he has earned my trust. But not everyone using heroku / aws / etc. have this same guy, trained by yourself, available. Thus, they use a service that makes that aspect of it invisible to them. Downtime still happens irregardless. >> I get to spend every minute of every work hour coding solutions. If you're a business owner and YOU still worry about hardware, then you need to fire your admins and hire rockstar-level admins. My admin spends no more than 2 hours a day on colo management because he does it the right way. Admittedly, I don't worry about it as much as I'd let on -- but there's still some aspects that I dig into by choice to make certain everything is in good working order, and that there are ample replacements on-site to mitigate the 'worst case scenario'. As a CEO, I fight on behalf of my users & clients daily, even if that means wasting mental bandwidth on what might be defined as someone elses' job. In a perfect world none of us would have to worry about hardware or downtime. Heroku is responsible for Heroku, and AWS is responsible for AWS -- and every user thereof is responsible for themselves and their operations. Colo. might be the answer for some of them, but it's not a perfect world either.

PythonDeveloper 14y ago
Well said.