3 ms·
>You seem to imply that there's a minimum latency between your personal machine and the "cloud" machines for the cloud term to apply. not latency, abstraction.
by notatoad 14y ago
>You seem to imply that there's a minimum latency between your personal machine and the "cloud" machines for the cloud term to apply.
not latency, abstraction. If i'm building a server out of parts and wiring it up in my closet, that's a server. If somebody else wires up a server in their closet and rents it out to me, that's a cloud. The cloud means not having to think about things like hard drives failing, and keeping hot spares of servers. So yes, that often means failover clusters but the real point of cloud is that it doesn't matter whether it's a cluster or not - the physical architecture is somebody else's problem.
- switch007 14y ago> If somebody else wires up a server in their closet and rents it out to me, that's a cloud. The cloud means not having to think about things like hard drives failing, and keeping hot spares of servers. Pre-cloud that was called "hosting" :P
- dhimes 14y agoInteresting thread. When I hear 'cloud' I assume multiple data-centers- a geographical diversity to mitigate against disaster.
- notatoad 14y agoI'd say a VPS could nominally be called part of a cloud, but most serious deployments, pre-cloud, were some sort of colo arrangement where if a hardware part died you had to either drive up to the DC and go swap out for a new one, or else call up the DC staff and ask them nicely to fix it for you. Your hosting wasn't a black box.
- switch007 14y agoI'm confused (and perhaps younger than you). It went like this: servers under desk -> colo -> vps/cloud/everything as a service? There wasn't a huge dedicated hosting market between colo and cloud?