Hi,
I have to make a presentation for a new design. I *know* that it will (erroneously) conjure up the "cloud" notion in some heads and need to come up with a simple way of describing why it is *not* so.
I've done other distributed designs so the concept of "depending on the wire" to make things work isn't foreign. I'm reasonably well versed in the advantages of such a design (as well as the drawbacks).
This presentation is a hybrid solution that works *on* the wire (even if that is an ethereal "wire") as well as *off* -- leveraging the features of each to produce a "better" solution.
The easiest distinction I can think of to clarify why this approach is *not* "cloud like" is to state that, with the cloud, you *rely* on the cloud's presence/accessibility to provide the functionality you desire. I.e., if the network goes down, you've got *squat*.
Does that seem a fair oversimplification?
Thx,
--don