“There are two ways of constructing a software design. One way is to make it so simple that there are obviously no deficiencies
and the other is to make it so complicated that there are no obvious deficiencies.” — C A R Hoare
How very witty, true and simple. Perhaps we could just follow this witty but actually very crucial IT Systems advice. Is IT that simple? Are we done here then ?
Well … perhaps not. I think, it is not that simple for the organization, to come to feasible Cloud Computing Architecture, also tailored for the Enterprise.
Especially if the “one” is a large corporation or any kind of large institutions. Any kind of IT enterprise which is currently severely exposed to myriad of mission critical but in the same time “deep legacy” systems. The kind of IT systems which are here to stay “forever” inside any given large organization today.
The really big issue hidden here is the one, we all dread and we all know is beneath:
Legacy systems are staying with us, “for good”.
All together with “legacy strategies”, vested interests and a such.
When faced with the Cloud marketing, “defenders of the legacy” (people and organizations) will surely mix-in an additional requirement and difficulty: One Cloud is not Enough! Meaning: no single Cloud Computing Vendor can produce an SLA that can satisfy. Very often (or always) it is claimed that due to compliance and security requirements, (which are sometimes pure assumptions), one Cloud provider can not satisfy.
There and then, will mushroom all sorts of reasons (some less true, some more), where Security and Compliance are unbreakable and unquestionable, and they will always come firmly on top of the list of the reasons of actually not going for the Cloud. And remember: Legacy IT is not secure and not compliant.
Thus the added (non) critical decision to be made: Single or multiple Clouds, public or private or any combination of the two. Saas? PaaS? IaaS? None of which can deliver the ever elusive “full compliance”.
Should we just give up then? Not yet.
Enterprise Cloud Agnostic Architecture
Continue reading “Feasible Cloud Computing Architecture (and implementation)”