Re: Someone Else's Computer certification
>Is your project going to be truly "steady traffic" 24x7, or does it have steady traffic only during the day? If you design for the cloud you could use much smaller servers and scale out as needed. Migrate to a bigger server instance size? Piece of piss.
And this is where cloud shines, if you'll pardon the pun. The *only* area it does.
>Also, what happens if your power goes out for several hours? Are you going to keep a UPS?
Depending upon colo, they'll have redundant power at the rack, the floor, or nothing. You can get a rackmount UPS, they're cheap. They may also have onsite batteries that take over before generators do. This is pretty common tech.
>Have you factored in the cost of electricity for this server?
I've not seen a ton of colos charge for power, they charge by the rack and then charge for bandwidth over a certain amount.
>Even with a colo, you are risking a long outage if they have a flood / fire / something you haven't thought of. So, you're gonna need two which are geographically apart.
You're risking the same thing with cloud. You need to put your application into different availability zones, georedundant, of course minding any laws applicable. Your application also needs to be able to handle that. Doing that without the cloud is also stupid simple, you can use a forwarding service like Akamai or Cloudflare, or even just DNS round robining. And you better hope that the regional outage, like S3 going down for all of South America, doesn't affect your multiple AZs.
>Cloud just takes away so many headaches. They have top class security (Not Azure though).
lmfao. Security in cloud is what you build into it. Also you have zero visibility into their internal layers, so you have no idea if it's paravirtualization or true virtualization, which can provide mitigating factors if someone bypasses the hypervisor. Plus the other parts like S3/Blobs/etc.
>Backups are super easy.
So are they with on-prem or even shared hosting.
>Power supply is reliable.
Ditto.
>Database administration is super easy.
Ah yes, because you can get a database on an engine that you have no direct control over.
>As much bandwidth as you can handle.
That you pay for. Same as with self-hosted.
>OTOH, it can be a confusing nightmare and they seem to release dozens of new services every month.
That doesn't scream reliability, that screams "sh!t changes all the time and you'll be scrambling to find the bug^H^H^H undocumented feature".