|
|
|
Browse Blog Posts by Tags
-
If you set out to devise a theoretical framework for both the design of distributed applications and the process of building distributed applications, it seems unlikely that you would base it on a theory for armed conflict. Even though we may talk of "death march" projects, I've never experienced any...
-
<Aside>This is good time to remind everyone that I don't work for PluralSight and they are not responsible for the content of this blog. Aaron Skonnard (who does work for PluralSight) graciously offered me this spot with the only proviso being that I use it. The opinions expressed here are mine...
-
Wherein our narrator makes a fortuitous discovery in a most unexpected place. One of the struggles I face in trying to explain my objections to the Indigo API is creating concrete examples of the abstract, and sometimes seemingly abstruse, notion I have that the Indigo API itself leads developers down...
-
In the comments, a couple of folks have responded to my criticisms of Indigo by suggesting alternative technologies for building distributed applications. I'm not looking for alternatives to Indigo. I'm working towards a better Indigo. I'm convinced that the underlying Indigo infrastructure can and should...
-
Steve responds to my Indigo complaints by claiming that Indigo, contrary to my assertion, has a simple messaging model. Although he doesn't specify exactly what he means, I assume he's talking about decorating methods with the [OperationContract(IsOneWay=true)] since that's what usually passes for simple...
-
Tom Fuller left a great comment on my last post. Mostly, it reminded me that I ought to be just as explicit about what's great about Indigo as I am about what's not so great. To answer Tom's specific question, the point of all this negativity is to influence the design of Indigo before it's released...
-
Wherein our plucky narrator reveals a shocking secret and makes a plea for understanding. I am Mort and I write distributed applications. I have decided that this simple fact is the primary factor in the difficulty I have communicating my concerns about WCF (nee Indigo). I've had several occasions to...
-
The key to giving good advice is knowing what matters most. It's possible to be 100% correct in what you say and still give stunningly bad advice if your focus is on the minutia of a topic. Rich Turner falls into this trap in his article over on MSDN called " Developing Distributed Services Today "....
-
The Holy Roman Empire was, as Voltaire famously remarked, "neither Holy, nor Roman, nor an Empire." Likewise, the [DataContract] in Indigo is neither data nor a contract. Moreover, like the putative Empire, the [DataContract] will never reach its rather ambitious goals, due to the inherent contradictions...
-
Death isn't on the line, so I feel safe going against Sam Marcuccio in this discussion . I'll start at the bottom of Sam's post and work my way up. The last line says "The really funny part of all this is, based on the argument, you'd never guess which on of these guys works for Microsoft". I know there...
-
Rich Turner doesn't believe SOA exists and challenges SOA advocates to draw him a picture: This applies to anyone out there - if you've got an architecture that will help solve real business problems, then show me the picture. Don't list products to me - show me the generally applicable architecture...
-
Clemens Vaster doesn't think SO Architecture is real . Roy Osherove agrees . Udi Dahan disagrees . Rich Turner and Sam Gentile seem to be squarely in "let's drop the A in SOA" camp. This all reminds me of a conversation I had with Ted Neward on his blog back in October . Before we get to the fundamental...
|
|
|
|
|
|