This post originated from an RSS feed registered with .NET Buzz
by Sam Gentile.
Original Post: Writing a New Service-Oriented Indigo Book
Feed Title: Sam Gentile's Blog
Feed URL: http://samgentile.com/blog/Rss.aspx
Feed Description: .NET and Software Development from an experienced perspective - .NET/CLR, Rotor, Interop, MC+/C++, COM+, ES, Mac OS X, Extreme Programming and More!
My feelings about writing a new book in the last 3 years are captured perfectly by Shawn; I also did not take my own advice and have signed a contract with Manning for a book tentatively titled “Service-Oriented Design with WCF.” Let me emphasize that this is not strictly an Indigo book and it is not at all like Pallman's book (we took it as a model of what not to do). My co-author and I wanted to tell a rigorous story about designing Service-Oriented and Asynchronous Messaging systems and oh by the way, here's how to do all that with Indigo. As Tomas said so well, “All the indigo advice is great, but where the intention of the book really shines is in making the technology be understandable and usable within the context of Service Oriented Architectures, and the advice and recommendations the authors can provide from this point of view. “Â The highest praise is when Don seemed to say that we should compare ourselves in the market to the master's book on Asynchronous Messaging! We should be so lucky to be even a tenth of the greatness of that work.
So what's our premise?
While acknowledging that terms like SOA are heavily over-hyped, we find a lot of value in SO concepts being applied to both the analysis and design of real systems delivering real business value. Our book takes a pragmatic approach, leaving the great debate on what is SOA for other books, showing instead how to leverage the Windows Communication Framework to build real systems that are service oriented. There are pragmatic decisions to be made about the use of technologies that wear the label SO and that is was we are aiming to be. It is intended that readers will be both Developers and Architects who are faced with the task of designing or developing Services that communicate within a Service Oriented Architecture (SOA). The book offers complete coverage of Indigo from this standpoint it should be fun to read rather than a strictly pedagogical treatise.Second it should be a Technology Enabler for Software professionals who are faced with the task of designing or developing Services that communicate within a Service Oriented Architecture (SOA). And lastly it should be a practical book rather than an Academic or theoretical effort
The term SOA has become ubiquitous in our industry. Unfortunately that has lead to massive hype that makes it difficult to understand and distinguish the real value of adapting SOA principles.In our judgment, the definition suffers from technology centric views that are based on the technology environment currently in use. We are taking a more pragmatic approach in this book and leaving the great debate to other books that can concentrate fully on that Zeitgeist. However, the term Service Orientation has a great deal of practical meaning in how one designs their Services, and to that end, WCF is Microsoft’s platform for building Service-Oriented applications or “Connected Systems.” So after presenting Service-Oriented concepts, we will show how to use these concepts in the context of Windows Communication Framework, drilling in deep
The Windows Communication Framework is simply Microsoft’s platform for creating Service-Oriented applications, or what Microsoft likes to call “Connected Applications.” As part of the new upcoming WinFX managed API, WCF presents a unified managed model and API for creating applications that talk to each other. In that regard, one of the most compelling advantages of Indigo is that, instead of a distributed developer being forced to choose amongst a bewildering array of stacks from Microsoft; ASMX, Remoting, COM+/ES, MSMQ, WSE and others, there is one unified programming model that offers all of the capabilities of the former stacks while moving ahead with an inter-operable stack and model that generates WS-* compliant SOAP messages that can offer connectivity with various other SOA platforms. Most notably in this book, we show interoperability with Java toolkits. And this very fact, in our opinion, is one of the greatest benefits of both SOA and Indigo; the ability to abstract existing functionality behind service boundaries on any platform and connect these “islands” together with Messaging and Indigo.
Previous Topic
