Is Indigo really *that* important?
There's clearly nothing that is so granular, so surgical, so "Einstein"
level elsewhere in the .NET stack. I get that. Its the Light Saber,,
the Bier Lambic, the Cassoulet Toulousain equivalent, if you will, of
the WinFX world. Naturally, the "Elvi" are bound to love it--
once they grok enough of it to sing about it -- since its hip, new and
happening. And it gives them endless ways to use the same n-many
nuggets of knowledge to solve just about any enterprise space problem.
And it certainly looks like its fun to talk about.
So, sure for them, its great. But what about Morts like me. What's in
Indigo for us? And why would we choose to engage in effort of using
and maintaining it over something like BizTalk or SQL Server Service
Broker and the SOAP bits we get using SQLCLR? Sure, its great that it
reduces the amount of code required to write a reliable messaging
application down from tens of thousands down to a few hundred. And
that's great if you're writing those frameworks, I guess. But what
other tools, tricks or abilities does it bring to the table?
That's why I agree with Jon Flanders (and indirectly Don Box) that
BizTalk is an extremely useful tool for the greater majority of
Professional Developers to grok, at least today. So are SSB and SQLCLR
for the Morts who can use them.
So, does anybody care to break Indigo down for me and tell me, from a Mort's POV, why its worth learning today?
And yes, I'm serious. While I have no aspirations to become an Indigo
"Einstein," I wouldn't mind being able to "Elvis: about it in the data
access and management space.