A blunt, completely unprofessional (and very accurate) analogy about Cloud Foundry

[UPDATED 11/09/15 – 9:43pm ET]

——————————

I recognize that some people might have been offended by the analogy used in this post. For that – I apologize.

It is never my intent to demean, or offend. It’s certainly not a reflection in any way against diversity or women’s rights, which are both important personal value for me, but also a deeply held EMC corporate value.

I shared my views on that topic on International Women’s day here (which like this post got overwhelming support, and some naysayers), and speaking as the executive sponsor for the EMC LGBT community during Pride Month here (which like this post got overwhelming support, and some naysayers).

Being a public figure, particularly a public senior leader at a large company means one must employ one of three approaches:

Completely keeping yourself out of the public sphere. I don’t think that works, after all a leader must be out there in front.
Censoring oneself constantly. Ultimately – this means you become corporate mouthpiece – bland, completely politically correct, and ultimately boring. Safe – but boring.
Being honest and open – being oneself transparently and authentically. But – this means sometimes causing offence, even if none is intended.

I will keep trying that last path. It means apologizing (rather than censoring) if/when I cross a line.

This blog reflects my own personal opinion – not the official viewpoint of EMC. I sincerely hope people get value out of Virtual Geek, and appreciate the tone and content that is sincere, transparent, and personal. But, as noted in the disclaimer of the post – that reinforces point – this is my personal opinion.

This gets blurry – as our personal and professional life is all intermingled. Point: Virtual Geek is not required reading for any EMCer.

I treasure the value of diversity, and of course those who disagree with me. That value of diversity is a personal opinion, but is indeed something valued at EMC. With diversity of thought, there will be many respected, and passionate people who will disagree with using a condom as an analogy.

I think we can disagree, discuss, debate – all without being disagreeable. Those debates and discussions are treasured – and when we do it together in a model of respect of different viewpoints, we all come out stronger. Freedom of speech means more speech rather than less. Political correctness to constrain speech is a dangerous path.

The topic of sexuality makes some people feel uncomfortable sometimes – yet of course is a part of the universal human experience. There’s great data here at the CDC regarding preventative measures for sexually transmitted disease. And, while I apologize if the analogy causes offence (and that’s not my intent) - it highlights why teaching people about methods to be in conscious control of their sex lives and make smart decisions about reproduction and sexually transmitted diseases is important (much MORE important than application deployment models to be sure – but very analagous – which is the point of the post :-).

Thanks for feedback, I’m listening! On to the blog post!

——————————————

Humans are funny. Stories work to spread ideas. Analogies help make complex ideas come through.

By definition - a story, an analogy - you loose technical detail, but they can make something come across VISCERALLY.

… Without further ado, here’s a base, blunt analogy about a complex topic: why structured PaaS, why open, how it relates to new workloads and public cloud choices….

"When it comes to your new Cloud Native App - protect yourself. Use a condom.

WHAAAAT?

Building an app directly to a public cloud’s APIs or data models is analogous to having loads of unprotected sex - may be fun and easy, but dangerous and not a good idea.

If you build an app that writes to any given cloud’s APIs or data structures (regardless of how “standard” you think those may be) that - you will have an unintended, accidental Cloud Native App baby.

Now - babies are a blessing.   An new “App Baby" can be a great blessing - but you’re better off to do this thoughtfully.

Cloud Foundry is an open structured PaaS layer that is part of the Linux Foundation. That means a customer can use as many public and private clouds they want with total protection from API lock in, and always have total workload portability.   They aren’t “locked in” with Pivotal Cloud Foundry in the same way that they aren’t “locked in” with any give Linux distribution.

The motto of Cloud Foundry could very well be “go ahead - have a lot of fun with Public Clouds – but don’t have an accidental cloud-specific app baby because you didn’t protect yourself".   Why? Because you don’t want to make decisions about babies and the next 20 years by accident.

You will be responsible for that little baby cloud app for the next twenty years. You might end up married to a Public Cloud that later on you come to regret (think of the lyrics to “Paradise by the Dashboard Light”). During that Cloud Native Apps late teenage years - perhaps even (GASP!) into it’s twenties, you’ll find yourself living with it and that particular public cloud.

Be smart. Protect yourself. Wrap that Cloud Native App rascal with Cloud Foundry so you can have safely have fun with as many Public clouds as you want - and build cool new apps faster and better.