For the last year, I have been meeting with customers and partners inside and outside the Microsoft ecosystem.
I have talked with friends that are involved, at different levels, with IT whether Dev or Ops.
I have been trying to explain what the public Cloud is, especially Azure, to many different people.
Of course, I have been using the same evolution charts we all seen everywhere to illustrate my speech and explain where I believe we are headed.
What hit me while speaking with all these different people were the recurring themes: I want/need/must start on the public Cloud, but how? Where do I start?
And very recently I finally found the right analogy, the one that will put your mind at ease, and allow you to relax and tackle the Cloud with some confidence. It has to do with someone reminding me of the Impostor's syndrome
The full MSDN library
Some of you will remember as I do, the golden days when we had a TechNet/MSDN subscription, and we received every month the full catalog of Microsoft products, on an indecent number of CD-ROMs. I don't know how you handled the amount of different products, but my approach was usually to fill the provided disc-book with the latest batch, and leave it at that. Occasionally, I would need to deploy a product and would pull out the matching disc.
Did anyone ever tried to grasp what all these products were and how to use them? I would venture to say that we certainly did not.
And yet, that is what some of us are trying to do with Cloud services. We get an overview of the services, quickly skimming over the names and vague target of each service, and we go home. The next day, we are willing to try new things and enjoy the breadth of options we have now a credit's card away.
And we are stuck.
Let's take an example, with what is named Cortana Analytics services. I chose this example because it is way out of my comfort zone, and I will not be tempted to go technical on you.
Here what the overview looks like:
When you were on the receiving end of the speech/session/introduction about these services, it all made sense, right?
What about now, do you have the slightest idea of what you could really do with Azure Stream Analytics?