« Sunsetting With InfoArchive | Main | Application Placement and the Business Value Chain »

May 20, 2014

TrackBack

TrackBack URL for this entry:
http://www.typepad.com/services/trackback/6a00e5500d4900883401a73dc46a16970d

Listed below are links to weblogs that reference Mathematical Mission Criticality:

Comments

Feed You can follow this conversation by subscribing to the comment feed for this post.

Bala Ganeshan

Is "Adaptivity" the ADM software EMC got from the nLayers acquisition? The biggest problem of the software (when I looked at it circa 2006-2007) was that they could not do packet inspection of traffic that goes over encrypted tunnels. Is that still the case?

Steve Todd

Bala - Adaptivity is an acquisition from 2013 and is different from nLayers.

Jeff Browning

As an attorney, I am frequently asked this question: "Is blah, blah, blah illegal?" To which I have a standard response: "The question of whether a given activity is illegal is uninteresting. A more interesting question is: What bad thing happens to you when you do blah, blah, blah?"

The question of whether a given application is mission critical is similarly uninteresting. A more interesting question is: "What bad thing happens to the business if the application fails?" And another interesting question: "How can we protect the business from the bad consequence of the application failing?"

In my experience, this varies dramatically based upon the nature of the application. For example, the failure of a typical Oracle application will result in severe consequences to the business. This is because of the nature of the beast: Oracle is spectacularly expensive. Thus, any customer in his / her right mind would only store very important data in that environment. Typically, Oracle manages the primary business data of the enterprise for this reason. Thus, loss of even a single Oracle transaction (say the trading instructions of a customer of a stock broker) would result in hard, severe legal consequences.

In this context (i.e. a traditional 2nd platform application like Oracle), concepts like backup, clustering, and remote replication all make perfect sense, and EMC has exceptional products to supply those needs.

A 3rd platform application is typically very different. Take MongoDB, an application with which I am fairly familiar. Mongo will consistently tell you: "You are going to lose some data. Get over it!" Thus, Mongo is not used for any purpose where transactional consistency is required. Usually, the customer will implement Mongo for an intermediate stage, scratchpad type of function. Also, Mongo datastores are often astronomically large. (Petabytes are common.) It is simply not possible to back up something that big.

Further, Mongo implements sharding, a geographically dispersed form of redundant replication. For this reason, the loss of a single Mongo server is simply uninteresting. No consequences occur at all from this, other than possibly a minor, temporary performance blip.

For these reasons, clustering, backup and remote replication are not very interesting for a 3rd platform application like Mongo (although there is some variability in that).

Therein lies the challenge for a company like EMC, which has traditionally dominated in the mission-critical 2nd platform types of applications, similar to Oracle. But then again, EMC has a long and storied tradition of reinvention. I have no doubt that EMC will eventually become one of the dominant players in the 3rd platform

The comments to this entry are closed.

Innovate With Global Influence


Innovate With Influence


by Steve Todd

EMC Proven

Blog powered by Typepad

Disclaimer

  • The opinions expressed here are my personal opinions. Content published here is not read or approved in advance by EMC and does not necessarily reflect the views and opinions of EMC nor does it constitute any official communication of EMC.