The document discusses private clouds and enterprise IT. It makes two main points. First, there may be a return to more centralized IT models as public clouds become more capable of supporting complex enterprise workloads. Second, we are addicted to old metaphors for technology and clouds will likely not resemble the common metaphors of "cloudbursting" or simple cloud hosting. The reality for enterprises will be hybrid cloud models that combine on-premise and on-demand services tailored to specific workloads and policies.
10. The abdication of
authority (and
responsibility.)
http://www.flickr.com/photos/abulic_monkey/
130899453/
11. You have no right
to an opinion
This is the pact of
on-demand IT
Abstraction means
abdicating your
right to architecture
One size fits all
meets Jack of All
Trades
http://www.flickr.com/photos/jamisonjudd/2433102356/
15. “Compared to the cost
of moving bytes around,
everything else is free.”
Microsoft technical fellow
Dr. Jim Gray, 2003
http://www-users.cselabs.umn.edu/classes/Spring-2009/csci8980-ass/Jim%20Gray.pdf
32. The startup: cloud hosting
Clouds are obvious
when you start
from scratch
3rd-party 3rd-party
Uncertain futures
payment service storage service
No capital at hand
High rate of
architectural
change Cache App Storage
tier tier tier
Let’s talk about cars for a minute. A car is a mode of transportation; but if you want to get from point A to point B, you have some decisions to make.=
There are lots of different car business models
At one extreme, you could be a car manufacturer. You’d have complete control over every aspect of your car, even though the cost of doing so would be very high. But you could still build cars from parts, and get them road-certified. It wouldn’t scale very well as demand increased, so this is the domain of hobbyists (who need high customization) or large manufacturers (who need economies of scale)
For most of us, the answer to transportation is to own a car. You’re not responsible for design – though you have some choice of models and features – but you are liable for everything. You have to finance it, maintain it, and so on.
If you’re a traveller, then you rent. This is a different model, with different responsibilities. You’re still at fault if you scratch or hit something, and still need to know directions, but someone else finances the deal and handles storage, cleaning, and other things. And you’re paying for what you use, not for the entire asset.
A car hire service abdicates even more control – you can still decide where to go and how to get there, pickup and dropoff times, etc., but everything else is the driver’s responsibility. You have only marginal control over the car model.
A taxicab takes this to the ultimate extreme: pay-as-you-drive economics, and nothing’s your fault provided you’re well behaved in the back seat. You have almost no control over the platform.
These are all degrees of abdication and abstraction. Sometimes a taxi makes sense – for example, when we’re going from place to place in a city. Other times, building our own makes sense – for example, if we’re landing on the moon.
This is a pretty obvious analogy to the computer industry. Sometimes, on-premise bare metal makes sense (and it’s expensive, but very customizable.) More likely, you’ll buy off-the-shelf components and define your own architecture. And other times, on-demand computing makes sense, either because of temporary workloads or because of elasticity.
But there’s a change in computing. The advent of virtualization has made us able to – in the analogy – retool the factory floor as needed. Atop our physical architecture, we have the ability to define virtual architectures suited to specific application workloads: OLAP processing, message queues, data analysis, batch computing, and so on.
This raises the question: where’s the abdication “sweet spot”? How do I find a tradeoff between “I want cloud efficiency and agility” and “I want to control it all”?
What we’re seeing is the emergence of a new class of mainframe – for an era where the business and the workload, not IT’s hardware and platform constraints, is driving the architecture. Large multi-cabinet devices, holding storage, processing, network, automation, and control systems look just like mainframes. But inside, they can be retooled on the fly by the business to accommodate workloads.
This simple fact dictates how we build computing architectures today. We put the UI out near the user, since that’s personal and unique – I’m looking at my flights on a Blackberry, you’re looking at yours on a desktop. Different content, different Uis.
But we put the shared processing and computing together, in the middle. To distribute information on all flights to all of us would be a nightmare; and the code that has to chew on all those flights needs to live near it to minimize data movement.
Let’s talk about cars for a minute. A car is a mode of transportation; but if you want to get from point A to point B, you have some decisions to make.=
I want to talk about the British pint.
Anyone know what this is?
The metric system makes sense
The metric system makes sense
An enterprise will adopt clouds opportunitstically. As utility services make sense, we’ll connect on-premise and on-demand platforms to one another.
An enterprise will adopt clouds opportunitstically. As utility services make sense, we’ll connect on-premise and on-demand platforms to one another.
An enterprise will adopt clouds opportunitstically. As utility services make sense, we’ll connect on-premise and on-demand platforms to one another.
This is about combining recipes and “composed designs” -- a concept that’s familiar to proponents of SOA.
When IT architects want to build something, they have a set of proven designs for doing so. A database is an example of this—it’s a combination of storage (disk) and a particular way of arranging things (tables and indexes) and language (structured query language, or SQL). We’ve learned that a database is a good prefab building block, so we use it. The alternative is to build it all, from scratch, writing to the disk itself.
When IT architects want to build something, they have a set of proven designs for doing so. A database is an example of this—it’s a combination of storage (disk) and a particular way of arranging things (tables and indexes) and language (structured query language, or SQL). We’ve learned that a database is a good prefab building block, so we use it. The alternative is to build it all, from scratch, writing to the disk itself.
When IT architects want to build something, they have a set of proven designs for doing so. A database is an example of this—it’s a combination of storage (disk) and a particular way of arranging things (tables and indexes) and language (structured query language, or SQL). We’ve learned that a database is a good prefab building block, so we use it. The alternative is to build it all, from scratch, writing to the disk itself.
When IT architects want to build something, they have a set of proven designs for doing so. A database is an example of this—it’s a combination of storage (disk) and a particular way of arranging things (tables and indexes) and language (structured query language, or SQL). We’ve learned that a database is a good prefab building block, so we use it. The alternative is to build it all, from scratch, writing to the disk itself.
When IT architects want to build something, they have a set of proven designs for doing so. A database is an example of this—it’s a combination of storage (disk) and a particular way of arranging things (tables and indexes) and language (structured query language, or SQL). We’ve learned that a database is a good prefab building block, so we use it. The alternative is to build it all, from scratch, writing to the disk itself.
When IT architects want to build something, they have a set of proven designs for doing so. A database is an example of this—it’s a combination of storage (disk) and a particular way of arranging things (tables and indexes) and language (structured query language, or SQL). We’ve learned that a database is a good prefab building block, so we use it. The alternative is to build it all, from scratch, writing to the disk itself.