Just Say No to 2.0

Just Say No to 2.0

  • Comments 8
Many IT pundits seem fascinated with versioning their bandwagons these days (yet another example of microwave mentality).  We have Web 2.0, BPM 2.0, Security 2.0 and, since we apparently need less clarity around the concept of SO, SOA 2.0.
 
Yefim Natis is a Gartner analyst who has been promoting SOA 2.0. Yefim thinks the negative reaction is good because it gets people talking about him and Gartner "demonstrates the interactive nature of Web 2.0".  (Apparently interactivity wasn't part of that tired, old Web 1.0.)
 
Architectural concepts aren't products so versioning them is a questionable practice.  I won’t go into details about what SOA 2.0 is supposed to be and why it should just go away - many others have already done a fine job of this. Duane posted a nice summary but I can't point to the specific post (thanks, Blogger).
 
Check out MacehiterWard-Dutton's online petition.
 
BTW - I joked about Workflow 2.0 in an earlier post - this term should not be taken seriously.
 
Leave a Comment
  • Please add 7 and 7 and type the answer here:
  • Post
  • Thanks a million for the link jevdemon - I feel funny calling you that but I can't find a link anywhere on the blog giving me any more info on your name!

    Anyway, thanks again - much appreciated,

    Tom
  • Hi Tom,

    I never realized my name wasn't on my blog! I just fixed this.   I hope your legal squabbles around Web 2.0 are behind you at this point!
  • Excellent John,

    thankfully the legal squabbles are over - it did no harm to the number of attendees at the conference mind!
  • Sounds like 2.0 2.0
  • How does this apply to .NET 3.0 which seems to be a version bump for similar reasons?
  • Rosyna,

    A fair question.  WinFX caused some confusion because many developers started asking "what about .NET"?

    .NET 3.0 is the new name for WinFX.  WinFX is a bundle of platform capabilities which includes Windows Communication Foundation (WCF), Windows Workflow Foundation (WF), Windows Presentation Foundation (WPF) and Windows Cardspace (WCS).    (There is a nice, short overview on Wikipedia here: http://en.wikipedia.org/wiki/WinFX.)

    The change from WinFX to .NET 3.0 is in name only and does not impact the technologies being delivered as part of the product (e.g. no namespace changes).  .NET Framework 3.0 is still comprised of the existing .NET Framework 2.0 components, including ASP.NET, WinForms, ADO.NET, additional base class libraries and the CLR, as well as new developer-focused innovative technologies in WPF, WCF, WF and WCS.  Soma has posted a blog entry about this name change here: http://blogs.msdn.com/somasegar/archive/2006/06/09/624300.aspx.  

    This is a controversial decision for many people because the underlying CLR is still 2.0 (see the comments on the entry above).  

    In summary, .NET 3.0 is simply a name change to better align thw capabilities of WinFX with .NET.  The name change does not impact any existing implementations (again,  no namespace changes).  

    Unlike SOA 2.0, .NET 3.0 actually adds significantly new functionality.   Many people (self included) believe the event-driven arguments made for SOA 2.0 are moot since this capabilty was already considered to be part of SOA.  Again, architectural styles are not products - versioning them is a questionable practice.

    Hope that helps.

    John

  • Look for my new book <i>Versioning 2.0: How Marketing Now Sells Concepts Instead of Products</i> from Microsoft Press.
  • Cute Jesse  :)

    As I stated earlier .NET 3.0 (nee WinFX) is a real "product" (actually a  bundle of platform capabilities) that includes WCF, WF, WPF and WCS.  The name change is a marketing initiative and has no technical impact upon any code you may already be developing.

    As for all the other 2.0 stuff out there, draw your own conclusions.

    John 2.0
Page 1 of 1 (8 items)