|Architecture >> IT Architect|
Service Oriented Architectures
|Language:||English||Source:||Other||Media:||Posted On:||18 Jun 09|
Welcome to the spring issue of JOURNAL. With this second issue we've gone global. This is a direct result of the tremendous feedback for JOURNAL1 from Microsoft's customers and partners, together with encouragement from colleagues worldwide. For that incredible vote of support I'd like to say 'Thank You'!
I am proud to have put together a team that believes unfailingly in the concept of a dedicated publication for IT architects and to have the support of some of the most 'agile' senior management in the business. With new sponsors, like Harry Pierson in Redmond, we will take this publication to a bigger audience and extend its reach through multiple delivery channels, including the web, digital download, and through MSDN Library, which becomes the long-term 'store' for JOURNAL. We will also reformat JOURNAL to support individual printing and easier on-screen reading.
Meet Harry; he's a smart thinker in the Platform Strategy and Partner Group in Microsoft, Redmond. He is determined to make JOURNAL available through as many channels as he can dream of, within limits of course. Harry has numerous ideas on how to widely communicate the writing of our authors who are first and foremost the soul of this publication. As editors, our mission is simple: Make sure our authors get heard. So JOURNAL is gearing up for massive reach and the ability to influence thinking about architecture, past, present and future.
We are fortunate to open this issue of JOURNAL with Pat Helland's first public written paper on Metropolis, which uses analogy and metaphor to explore the present and future directions of IT by studying the recent history of our urban centers. Pat's reputation is formidable and as the Architect lead for COM+ and SQL Server Broker past experience tells us that if he has something to say it's probably worth listening to. Metropolis is part of his ambition to write a book on SOA and 'autonomous computing' therefore we expect more papers from Pat will appear in future issues of JOURNAL as his ideas make their way from incubation to ink.
Lawrence Wilkes and Richard Veryard, from their think tank CBDI Forum, remind us that for all the hype surrounding SOA we must not forget that the objective is to build agile systems in support of the business. Sometimes we get so carried away with the compelling power of emerging Web services technology that we need to be brought back to earth again. Their list of principles and best practices does just that.
Easwaran Nadhan from EDS demonstrates how companies must progressively construct components and services involved in the implementation of SOA. He postulates that a road map and company-specific standards are key prerequisites ensuring systematic implementation of such enterprise wide architectures. He identifies eight key challenges a company faces in SOA implementation and uses real-world examples to address these challenges.
Microsoft's Philip Teale and Robert Jarvis of SA Ltd introduce the first part of a paper discussing business patternsódefining architectural templates for business solutions. They identify a set of architectural elements required to fully describe business patterns. This set has been classified and focuses on elements that describe the most stable parts of a business suitable for subsequent "patternisation". Part two of this paper will appear in the next issue of JOURNAL.
Soumen Chatterjee from CGE&Y gives us a description of messaging patterns in SOA. Traditionally messaging patterns have been applied to enterprise application integration solutions, but Soumen uses these patterns to explain how a SOA can be implemented. His insight shows us that messaging patterns can be applied equally well at the application architecture level, especially in SOA-based solutions, because they too are fundamentally message-oriented. See the next issue of JOURNAL for part two.
Tags: Enterprise Architecture, EA, Architecture, SOA, eBook, Microsoft, Journal, Service, .net, MetaData, architecturejournal, [SUGGEST A TAG]