« VMworld 2010 Session Content Part 1 - Impending Data Explosion | Main | »

September 10, 2010


Jonas Irwin

Very interesting take on where things are going. I've thought about this too and, like you've suggested here, the story always starts to fall apart when the I get to the idea of co-locating or moving the database layer out to an external provider.

With the way you've mapped things out here, wouldn't latency between the external provider and the internal database cloud become a big issue? Does such a model suggest metro level locality between the various application tiers? Perhaps some kind of a database caching mechanism at the external cloud provider would make sense?

I haven't seen a customer acctually do something like this yet - either everything is hosted in one place or they use platform as a service offering that provide a sort of generic (usually open source based) database service.

The comments to this entry are closed.

Powered by TypePad
View Jeff Browning's profile on LinkedIn

disclaimer: The opinions expressed here are my personal opinions. I am a blogger who works at EMC, not an EMC blogger. This is my blog, and not EMC's. Content published here is not read or approved in advance by EMC and does not necessarily reflect the views and opinions of EMC.