What exactly makes something “mission critical”?

Pete Welcher wrote an excellent Data Center L2 Interconnect and Failover article with a great analogy: he compares layer-2 data center interconnect to beer (one might be a good thing, but it rarely stops there). He also raised an extremely good point: while it makes sense to promote load balancers and scale-out architectures, many existing applications will never run on more than a single server (sometimes using embedded database like SQL Express).

He’s right ... but then you have to ask your CIO what exactly makes something “mission critical” and why it would be necessary to implement L2 DCI and risk the stability of a VLAN (or even a whole data center, depending on how bad your design is) just to increase the uptime of such a brittle kludge by transporting it between data centers intact (while it’s quite probable that it will implode on its own without being touched or moved). It might make more sense to be pragmatic, acknowledge that some applications will never be highly reliable and live with the consequences.

You can read a bit more about this topic in the “Long distance vMotion = traffic trombone, so why go there?” article I wrote for SearchNetworking; numerous details will also be covered in the Data Center Interconnect webinar (register here).

1 comment:

  1. Pete Welcher's article, "Data Center L2 Interconnect and Failover" is reachable via a different url now: http://www.netcraftsmen.net/blogs/entry/data-center-l2-interconnect-and-failover.html


You don't have to log in to post a comment, but please do provide your real name/URL. Anonymous comments might get deleted.

Ivan Pepelnjak, CCIE#1354 Emeritus, is an independent network architect. He has been designing and implementing large-scale data communications networks as well as teaching and writing books about advanced technologies since 1990. See his full profile, contact him or follow @ioshints on Twitter.