The Agile Architecture Revolution: How Cloud Computing, REST-based SOA, and Mobile Computing are Changing Enterprise IT
A sneak peek at upâ€“andâ€“coming trends in IT, a multidimensional vision for achieving business agility through agile architectures The Agile Architecture Revolution places IT trends into the context of Enterprise Architecture, reinventing Enterprise Architecture to support continuous business transformation. It focuses on the challenges of large organizations, while placing such organizations into the broader business ecosystem that includes small and midsize organizations as well as startups. Organizes the important trends that are facing technology in businesses and public sector organizations today and over the next several years Presents the five broad organizing principles called Supertrends: location independence, global cubicle, democratization of technology, deep interoperability, and complex systems engineering Provides a new perspective on serviceâ€“oriented architecture in conjunction with architectural approaches to cloud computing and mobile technologies that explain how organizations can achieve better business visibility through IT and enterprise architecture Laying out a multidimensional vision for achieving agile architectures, this book discusses the crisis points that promise sudden, transformative change, unraveling how organizations spending on IT will continue to undergo radical change over the next ten years.
Yogish Pai: One of the best practices for Enterprise Architecture teams to redo the enterprise road map on a periodic basis. It is typically reviewed and updated during the yearly budgeting cycle and my preference is to perform this activity every 18 months. The best practices (and the traditional approach) is to first document the as-is, next develop the target or future state (architecture) and finally develop a short term (6 months), mid term (12 months) and long term (18 months) road map. Preferable an actionable road map that ties back to the business initiatives.
Implementing Service Oriented Architecture at the Canada Institute for Scientific and Technical Information
Anthony, Stephen K. The Serials Librarian, 55(01-02), pp. 235 - 253. As they seek new roles in the digital realm, libraries are finding it increasingly difficult to manage the complexity of technology implementation while continuing to cost-effectively meet their mandates as information providers. Many organizations find themselves dealing with legacy, isolated, duplicated and ineffective information systems. The practices of enterprise architecture and service oriented architecture hold much promise as methodologies to reduce complexity, to encourage and enable collaborations, and finally to rein in the beast of technology. Even libraries under budgetary constraints can benefit from knowledge of enterprise architecture and service oriented architecture best practices.
Neil Ward-Dutton, July 24, 2008: Via Service Oriented Enterprise, I recently picked up an Infoworld blog post by SOA journeyman David Linthicum, where he makes a couple of very strange points about SOA and ESBs. It may be, of course, that the post is pure link bait: certainly, David appears to have said some relatively sane things in the past, so that might be it. If it is link bait, I'm going to fall for it now.
Draft 2.0 of The Open Group's SOA ontology. This draft is being exposed for comment outside The Open Group prior to formal Open Group company review. Interested parties are invited to sent comments, and those comments will be addressed in the version submitted to formal review by The Open Group. A PDF file contains the textual description of the ontology, and an OWL file contains the ontology itself.
Author Geoffrey Moore explains how SOAs will become the underlying force of the new data center.
Stew Welbourne: Yet more circular debate about whether SOA is just hype or whether it offers anything of value. It's addictive reading, not that I expect anyone to reach a definitive answer, but moreso to observe the correlation between the debating individual, the scope of his/her problem-space, and his/her corresponding position on whether SOA is hype or not. The relationship between Enterprise Architecture and SOA (and here I have just detatched a seprate thread about EA and Hype!!) is significant in my opinion as a result of the hugely important question of scope. The good old example of the difference between an Enterprise Architect and a System or Application Architect is the analogy with Town Planners and Building Planners. In simple terms Enterprise Architects are focusing at the optimal arrangement of buildings and utilities over a large area, whereas System/Application architects are focusing on the optimal construction of a small number of buildings and their optimal interfacing with the utilities they assume will be there at some point.
Service-Oriented Architecture (SOA) is a way of organizing software. If your companyâ€™s development projects adhere to the principles of SOA, the outcome will be an inventory of modular units called services, which allow for a quick response to change. This book tells the SOA story in a simple, straightforward manner that will help you understand not only the buzzwords and benefits, but also the technologies that underlie SOA: XML, WSDL, SOAP, XPath, BPEL, SCA, and SDO. And through it all, the authors provide business examples and illustrations, giving a practical meaning to abstract ideas.
This book demonstrates service-oriented architecture (SOA) as a concrete discipline rather than a hopeful collection of cloud charts. Built upon the author's firsthand experience rolling out a SOA at a major corporation, SOA in Practice explains how SOA can simplify the creation and maintenance of large-scale applications. Whether your project involves a large set of Web Services-based components, or connects legacy applications to modern business processes, this book clarifies how -- and whether -- SOA fits your needs.
Today, business processes and information systems are so tightly intertwined that they must be designed together, as parts of a total architecture, to realize enterprise goals. In Succeeding with SOA, Paul Brown shows how service-oriented architectures (SOAs) provide the best structure for such integration: clean, well-defined interfaces between collaborating entities. But even SOAs need to be correctly understood and implemented to avoid common failures. Drawing on decades of experience, Dr. Brown explains what business managers and IT architects absolutely need to know--including critical success factors--to undertake this essential work.
Information Technology professionals can use this book to move beyond the excitement of web services and service oriented architecture (SOA) and begin the process of finding actionable ideas to innovate and create business value. In Enterprise SOA: Designing IT for Business Innovation, SAP's blueprint for putting SOA to work is analyzed from top to bottom. In addition to design, development, and architecture, vital contextual issues such as governance, security, change management, and culture are also explored. This comprehensive perspective reduces risk as IT departments implement ESA, a sound, flexible architecture for adapting business processes in response to changing market conditions. Based on extensive research with experts from the German software company SAP, this definitive book is ideal for architects, developers, and other IT professionals who want to understand the technology and business relevance of ESA in a detailed way - especially those who want to move on the technology now, rather than in the next year or two.
In The New Language of Business, senior IBM executive Sandy Carter demonstrates how to leverage SOA, Web 2.0, and related technologies to drive new levels of operational excellence and business innovation. Writing for executives and business leaders inside and outside IT, Carter explains why flexibility and responsiveness are now even more crucial to successâ€“and why services-based strategies offer the greatest promise for achieving them. Youâ€™ll learn how to organize your business into reusable process componentsâ€“and support them with cost-effective IT services that adapt quickly and easily to change. Then, using extensive examples - including a detailed case study describing IBMâ€™s own experience - Carter identifies best practices, pitfalls, and practical starting points for success.
This book spells out guidelines and strategies for successfully using Service Oriented Architecture (SOA) in large-scale projects. SOA represents the latest paradigm in distributed computing and middleware development. However,SOA is not a revolution, but rather an evolution in software architecture. SOA is a collection of best practice software construction principles accompanied by proven methodologies in development and project management. This book is unique in that it offers a pragmatic approach to the topic. The authors borrow from their more than forty years of collective enterprise experience, and offer a frank discussion of the challenges associated with adopting SOA. They also help readers ensure that their organization does not become too closely tied to a specific technology. The result is a detailed introduction to the topic and an architectural blueprint for implementing SOA.
Targeted at management, the first six chapters of Secrets of SOA focus on the business impact of service-oriented architecture technological decisions with an emphasis on cost, flexibility, and the ability to maintain business objectives. Each of the six chapters explores a different topic that illustrates the value of a physically integrated SOA infrastructure organized at the enterprise level. Taken together, they demonstrate why enterprise-level planning, backed by a centralized deployment strategy, is essential to the success of SOA. Aimed at the IT executive, the second half of the book deals with specific IT issues raised by SOAs and why these issues are best dealt with on an enterprise level. Among the topics covered in these eight chapters are virtualizing resources, managing heterogeneous workloads, maintaining data and transactional integrity, and the value of proximity.
Authors Jason Bloomberg and Ronald Schmelzer - senior analysts for IT advisory and analysis firm ZapThink - say it all in the title of their new book, Service Orient or Be Doomed!: How Service Orientation Will Change Your Business. That is, if you fail to service orient your company, you will fail in competing with the organizations that do. This provocative new book takes service orientation out of its more familiar technological surroundings within service-oriented architecture and introduces it as a philosophy that advocates its rightful place within a business context, redefining it as a new way of thinking about organizing your business and its processes. Informal, challenging, and intelligent in style, Service Orient or Be Doomed!: How Service Orientation Will Change Your Business shows you how you can best use technology resources to meet your company's business goals and empower your company to go from stuck to competitive.
Companies face major challenges as they seek to flourish in competitive global markets, fuelled by developments in technology, from the Internet to grid computing and Web services. In this environment, service orientation - aligning business processes to the changing demands of customers - is emerging as a highly effective approach to increasing efficiency. In this book, Paul Allen provides an accessible guide to service orientation, showing how it works and highlighting the benefits it can deliver. The book provides an integrated approach: after covering the basics of service orientation, he discusses key issues such as business agility, designing quality-of-service infrastructure, implementing service-level agreements, and cultural factors. He provides roadmaps, definitions, templates, techniques, process patterns and checklists to help you realize service orientation. These resources are reinforced with detailed case studies, from the transport and banking sectors. Packed with valuable insights, the book will be essential reading for CIOs, IT architects and senior developers. IT facing business executives will also benefit from understanding how software services can enable their business strategies. Paul Allen is a principal business-IT strategist at CA and is widely recognized for his innovative work in component-based development (CBD), business-IT alignment and service-oriented architecture. With over thirty years experience of large-scale business systems, he is an established author whose previous book was the critically acclaimed 'Realizing e-Business with Components'. Sam Higgins is now with Forrester Research Inc.; formerly he managed the Innovation and Planning Unit of Queensland Transport's Information Services Branch. Paul McRae is the application architect in the Innovation and Planning Unit of Queensland Transport's Information Services Branch. Hermann Schlamann is a senior architect in the architecture group of Credit Suisse.
In this developerWorks Series book, IBM Enterprise Integration Team experts present a start-to-finish guide to planning, implementing, and managing Service-Oriented Architecture. Drawing on their extensive experience helping enterprise customers migrate to SOA, the authors share hard-earned lessons and best practices for architects, project managers, and software development leaders alike. Well-written and practical, Service-Oriented Architecture Compass offers the perfect blend of principles and "how-to" guidance for transitioning your infrastructure to SOA. The authors clearly explain what SOA is, the opportunities it offers, and how it differs from earlier approaches. Using detailed examples from IBM consulting engagements, they show how to deploy SOA solutions that tightly integrate with your processes and operations, delivering maximum flexibility and value. With detailed coverage of topics ranging from policy-based management to workflow implementation, no other SOA book offers comparable value to workingIT professionals. Coverage includes SOA from both a business and technical standpointâ€“and how to make the business case; Planning your SOA project: best practices and pitfalls to avoid; SOA analysis and design for superior flexibility and value; Securing and managing your SOA environment; Using SOA to simplify enterprise application integration; Implementing business processes and workflow in SOA environments; Case studies in SOA deployment; and After you've deployed: delivering better collaboration, greater scalability, and more sophisticated applications
This is a comprehensive tutorial that teaches fundamental and advanced SOA design principles, supplemented with detailed case studies and technologies used to implement SOAs in the real world. All major software manufacturers and vendors are promoting support for SOA. As a result, every major development platform now officially supports the creation of service-oriented solutions. Parts I, II, and III cover basic and advanced SOA concepts and theory that prepare you for Parts IV and V, which provide a series of step-by-step how to instructions for building an SOA. Part V further contains coverage of WS-* technologies and SOA platform support provided by J2EE and .NET.
Mashup Corporations: The End of Business As Usual tells the tale of Vorpal Inc., a company that pioneers the implementation of service-oriented architecture to transform its business model. CEO Jane Moneymaker believes in marketing manager Hugo Wunderkind's idea of creating a new market using non-traditional methods based on mashups, but struggles to achieve this vision. The story illustrates what it takes to achieve cultural change, overturning established business and IT structures. By embracing a service-oriented approach Moneymaker makes Vorpal faster, flexible and more responsive, bringing an end to business as usual. Mashup Corporations takes a unique approach to communicating its message. From the first page, readers will find themselves in a story populated with people who interact in ways that will ring true to others who have struggled to make technology work in an organization, large or small. The conflicts that naturally arise between CEOs, CIOs, and line of business managers illustrate the important issues at stake within Vorpal and most other companies. As the leaders of Vorpal find their way out of their predicament, rules about how mashups and service orientation can be properly applied emerge. These rules, which may be the most enduring contribution of the book, are illustrated and analyzed using real-life examples.
The Role of Event Processing in Modern Business. In eBizQ, 30 July 2007. By Dr. K. Mani Chandy, Simon Ramo Professor of Computer Science, California Institute of Technology and Roy Schulte, Vice President and Distinguished Analyst, Gartner, Inc. Almost everyone wants to have an adaptive enterprise, a company that runs faster and smarter because it has "situational awareness," can "sense-and-respond" to opportunities and threats, and can "track-and-trace" items as they go through their life cycles. What do these three capabilities have in common? They are all achieved through event processing.
Service-Oriented Architecture (SOA): A Planning and Implementation Guide for Business and Technology
Amazon: The book shows you how to plan, implement, and achieve SOA value through its prescriptive approach, joining the business and strategic perspective to the technical and architectural perspective. Applicable to all industries, technology platforms, and operating environments, this innovative book provides you with the essential strategies to drive greater value from your SOA and realize your business goals.
By Darryl K. Taft, 15 July 2007. Dan Cahoon was looking for a way to streamline staffing operations at tax company H&R Block, the nation's largest seasonal employer. Rather than use traditional desktop-based software for the job, the senior systems architect at H&R Block was able to deliver SOA-connected AJAX portlets to more than 12,000 branch offices for temporary work spaces to meet the company's staffing needs.
Jesus Rodriguez and Javier Mariscal, @ SOA WORLD MAGAZINE. A well-planned Web Service interoperability environment begins by clearly defining who your Web Service consumers are now and in the future. There was a time not so long ago when you could count on a fairly homogenous consumer population. This was about the same time that you were happy just to be able to get a Web Service running in the first place and finding a consumer who could actually interact with your Web Service was cause for celebration. Those days have changed however and Web Services interoperability, once a "fancy" addition to your SOA design, is now a key and indispensable requirement in most SOA scenarios.
By Anant Kadiyala. SOA WORLD MAGAZINE, Jun. 28, 2007. With the emergence of Web 2.0 and SOA technologies, mashups have gained in popularity. Web 2.0 provides a rich user experience, and SOA technologies facilitate the underlying flexible plumbing required to make mashups happen. So you could say mashups are a mashup of Web 2.0 and SOA!
Book by Steve Jones published on Sep 26, 2006 by InfoQ. Major changes in technology have not been driven by the technologies themselves but by the change in thinking that they enabled. OO design changed software by changing thoughts away from procedures and onto real world "things". This book argues that for SOA to succeed we must move our thoughts away from the implementation technologies and towards the "what" of the business. Using a straight-forward, pictorially driven, methodology the book explains who to discover what the business services really are and how to construct an overall business service architecture.
By Bob Violino, CIO.com. Facing too many emerging standards -- and not enough vendor support for them -- in your service-oriented architecture implementation? Consider these steps in your planning. While the potential benefits of SOA are clear, like the ability to reuse existing assets, the standards picture looks anything but settled. Not only did Forrester Research count some 115 standards floating around SOA and Web services in its most recent study on that topic, but also, it found that just confirming which vendors support which standards is nearly impossible. Yet CIOs must press ahead with SOA projects in order to meet business needs. Hong Zhang, director and chief architect of IT Architectures and Standards at General Motors, has been balancing the standards dilemma with ongoing SOA work for several years.
David Linthicum: Working directly on SOA projects as an independent I'm exposed to many more organizations than when I was building technology. As such, I see some common patterns or issues emerging.
Interoperability is an important factor in the success of solutions that are based on Web Services and Service Oriented Architecture (SOA), along with other key factors such as contracts, loose coupling, and reuse. Interoperability is generally accomplished by developing your Web Services using the well-established guidelines for implementing Web Services and by following industry standards such as XML, WSDL, SOAP, and UDDI. However, just following Web Services standards and guidelines during the development phase of a project isn't sufficient to achieve interoperability.
Service Oriented Architecture (SOA) facilitates the development of applications as modular business services that can be easily integrated, secured, and administered. Benefits of an SOA approach include more-rapid development, decreased maintenance and change management costs, and improved business visibility. However, achieving these benefits isn't automatic - although many early adopters of SOA have been able to realize its promise fully, others have struggled to find the best architecture and design patterns for this approach.
Service Oriented Architecture (SOA) is at the heart of many major IT initiatives and vendor offerings. However, while SOA has the potential to deliver business value through streamlined application integration, as well as integration with partners and suppliers, the open nature of SOA has the potential to cause problems with Sarbanes-Oxley compliance. This article will look at compliance issues inherent in developing an SOA. Using a practical example, we'll examine COSO Control Objectives, Risks, and their supporting IT systems from the perspective of Sarbanes-Oxley compliance.
After almost 14 months of intense work, over 6000 messages posted to hundreds of threads, 6 face to face meetings and 34 conference calls by over 225 members and observers from approximately 89 different companies, the first true public standard to describe SOA now exists. The OASIS SOA RM TC closed a final ballot with a successful majority vote to unanimously approve the current draft as an official OASIS Reference Model for SOA Committee Specification. The Reference Model is not itself Architecture, it is more like a template to guide archtiects. Unlike most definitions of SOA which rely on specific examples, the SOA RM is also entirely abstract and not tied to any one technology family or specifications. Those architecting SOA or BPM as the governance layer over top of SOA will probably find it the most useful as it points out the entities and patterns required to allows SOA to work and support the governance layer.
(Found in a blog, "Versioning is as inevitable as security.") SOA development practice isn't much different from other software development practices except for design and maintenance. Multiple self-containing and aggregated services that interact with others have their own lifecycle and evolution. The loosely coupling model of SOA services significantly simplifies design but creates additional difficulties in maintenance, especially in the interoperability of different service versions
Many forces are involved with architecture, but the fundamental principles that govern all architectures are simple: itâ€™s easy, it works, itâ€™s familiar, and it can be trusted. The purpose of this book is to let you form your own opinions about the impact of services orientation on your business and computing environments. This book is not trying to be an authoritative reference for service orientation. Rather, presented here is an interesting set of classical papers on architecting services by a variety of well-known authors in the architectural space. The topics, or architectural viewpoints covered, go from a perspective on business architecture, through model-based tools, to map from the business to technology to the choices in new IT infrastructure.
Many SOA initiatives were launched this year, each with its own set of goals and expectations. Some failed miserably, while others failed just a little. For many, the determining factor in fulfilling their original objectives was drawing upon the experience of those who had already survived projects with less fortunate results. These individuals lived to tell their stories and warn others of what lies ahead along the path toward SOA. In our line of work we get pulled into various projects at different stages of completion. Weâ€™ve seen good SOA go bad and bad SOA get even worse. Problems can be fixed and mistakes can be undone, but of course there is always an impact to getting things back on the right track. The best course of action is, obviously, avoiding problems and mistakes in the first place. Understanding the pitfalls others have fallen victim to, puts you in a position from which you can form the extent of foresight required to chart a safer route down your own SOA roadmap. To help you get a head start, we have collected the eight most common SOA adoption pitfalls of 2005.
Jeff Schneider is noticing something really interesting about SOA adoption. You can put the adopters in 4 buckets: 1. Companies that don't do SOA and have no intention of doing it; 2. Companies that don't do SOA but keep talking about it and have mastered the blame game; 3. Companies that do SOA, but poorly; and 4. Companies that do SOA and reap huge benefits
Book published by Packt Publishing in June 2006. Ten practical real-world case studies combining business process management and web services orchestration. Real-world BPEL recipes for SOA integration and Composite Application development. Combining business process management and web services orchestration. Authors: Matjaz Juric, Stany Blanvalet, Jeremy Bolie, Michael Cardella, Sean Carey, Praveen Chandran, Yves Coene, Kevin Geminiuc, Arun Poduval, Lawrence Pravin, Jerry Thomas, Doug Todd, The Hoa Nguyen, Markus Zirn, Harish Gaur
As Service Oriented Architecture (SOA) initiatives attain critical mass in the enterprise, there's more and more interest in boosting business results and competitiveness (not to mention leveraging significant long-term investments) by incorporating mainframe assets into the SOA. However, if this attention is myopically focused on data and functionality, companies may be overlooking the mainframe's highest potential for rapid time-to-market and ROI: the value of the expertise resident with mainframe developers.
Service Oriented Architecture Modeling News. Public construction of an enterprise SOA is being conducted on this web site. Public participation is welcome. The enterprise SOA implementation will be a Global Response System for disaster relief. This effort will adhere to the OASIS SOA reference architecture developed by the OASIS SOA Reference Architecture subcommittee of the OASIS Reference Model technical committee. Click here for the description and goals of the Global Response System.
Approaches to Web enablement of legacy systems By Martyn Hill, SOA Web Services Journal. Mar. 19, 2006
Tim Bray's comments on Web Services at a Crossroads by Daryl Plummer
Web services have evolved from plain application-integration enablers to value-added stand-alone functionality providers such as getting a quote to a comprehensive business function like processing orders. Enterprises are exploiting this new revenue model by offering such business functions as services on usage basis. Information sharing instances such as Amazon's e-commerce services have helped in the creation of new powerful solutions using business functions as services. By Naveen Kulkarni; Manivannan Gopalan; Geo Philips Kuravakal; Lipika Sahoo; Sunny Saxena, in SOA Web Services Journal, February 27, 2006.
In this second article about service-oriented architecture (SOA), Stephen Bennett offers a concrete plan. SOA Web Services Journal, Feb. 27, 2006
One of the business benefits organizations strive to achieve by implementing a service-oriented architecture (SOA) or in utilizing Web services is the opportunity to reuse business components. Asset reuse is one of the core drivers of the SOA or Web service ROI calculation. Although leveraging the service concept provides an avenue for application consolidation and reuse, these same efficiencies also introduce a distinct level of business risk.
A critical piece of a service-oriented architecture. By: Ivan SOA Web Services Journal. Chong; Ashutosh Kulkarni. Feb. 24, 2006
By JP Morgenthal. Column DMReview, January 26, 2006
In a service-oriented architecture (SOA), a service is a unit of work performed by a service provider to achieve desired results for one or more service consumers. A service provides a function that is well defined, self-contained (for example, loosely coupled to its environment), described solely by its interface contract and behavioral attributes (for example, it hides implementation), and located anywhere on the network.
This chapter takes the next step toward execution by focusing on how to plan an SOA project. The topics in this chapter constitute the best practices the authors have uncovered for forming a project office, how to define the phases of SOA adoption, the need for and mechanisms of SOA governance, and finally, the various project roles and how they interact with each other. From the Book Service Oriented Architecture Compass: Business Value, Planning, and Enterprise Roadmap. By Sanjay Bose, Norbert Bieberstein, Marc Fiammante, Keith Jones, Rawn Shah.
IBMs Bob Sutor explains his view on service-oriented architecture. ebizQ January 2004. Registration required.
Introducing a New Service-Oriented Architecture Maturity Model
Service-Oriented Architecture (SOA) has gained widespread acceptance in the enterprise architecture space over the past five years. The constant pursuit of business logic reuse and application ROI seems to have come with little consideration for the hidden costs. This article will go into detail on what everyone in your company needs to know before planning to implement a SOA. By Tom Fuller, ASPAlliance 23 Aug 2005.
Learn advanced BPEL concepts and best practices for development, deployment, and administration from the architects implementing them in real-world applications.
"Right now the biggest gotcha with SOA is market confusion and lack of understanding," says Teresa Jones, a senior research analyst at Butler Group. "Vendors could promise to deliver SOA and fail, because their technology is just one facilitator to SOA."
Terms such as grid, on-demand, and service-oriented architecture are mired in confusion, but there is an overarching trend behind them all. ACM Queue vol. 3, no. 6 - July/August 2005 by Ian Foster, Argonne National Laboratory and University of Chicago, Steven Tuecke, Univa
Microsoft's SOA journal, July 2005. Articles in this issue include one on Metropolis and SOA Governance and one on Value-Driven Architecture.
The Achilles' heel of service-oriented architectures (SOAs) has been policy enforcement. A standard is emerging for run-time control: the Governance Interoperability Framework (GIF). Web Services Pipeline, 1 June 2005.
Each of these technologies by itself can add much value to any IT shop, but when used together they can put you well on your way to technology nirvana. Web Services Pipeline, 8 April 2005.
Implementing a major new corporate IT system right isn't easy. A well-designed system can boost business effectiveness and contribute directly to the bottom line. By Dr. Chris Harding, The Open Group, 24 April 2005
Developing a core reference model to guide and foster the creation of specific, service-oriented architectures
Two of the most-heard acronyms today are SOA (for service-oriented architecture) and ESB (for enterprise service bus). Our man Tarak delves into what these terms actually mean, and points out the ways that these two architectural concepts, in particular, when used together, can help enterprises match business goals with technology implementations.
The enterprise architecture framework is widely used as a mechanism to manage the development and evolution of architectures. In this article we introduce a generic approach to integrating the SOA framework requirements with existing frameworks. By David Sprott and Lawrence Wilkes
Mike Gilbert compares SOA and EDA
Jeff Schneider, Service Oriented Enterprise
There are substantial differences between SOA and BPM -- differences that can have broad-ranging effects on the organizations that deploy them. SOA addresses the technology need for agility and adaptability, while BPM addresses both the business and the technology needs. BPM Today, 22 Feb, 2005.
When implementing an SOA, it is critical to address the techniques required for the identification, specification and realization of services, their flows and composition, as well as the enterprise-scale components needed to realize and ensure their quality.
Aaron Skonnard's take on service orientation and what it means to the enterprise as well as to the developer. MSDN Magazine, February 2005
Stephen O'Grady. RedMonk Study, 12th August 2004. (PDF)
Column by Clive Finkelstein in DMReview.com January 1, 2005.
The premise behind the service-oriented architecture is relatively simple â€“ standardise the generic functions that are widely used by many applications into reusable components (services) that are accessible over a network, and code more specific logic needs into the application itself. Computerworld Singapore, 24 August 2004.
This white paper presents the Microsoft Corporation vision for service orientation and service-oriented architecture in enterprise computing. (18 printed pages) .NET Architecture Center, July 2004.
Although SOA is 'top of the toy box' this year, it's by no means well understood. One of the big issues is that few of the vendors can resist the temptation to re-badge all of their existing products and services as SOA, just because they are Web Service enabled. Is that reasonable? We don't think so - there's a great deal more to SOA than the interop layer. This week we apply a metaphorical thermometer to gauge the temperature of SOA thinking, platforms and practices.
Experience from first Service-Oriented Architecture (SOA) implementation projects suggest that existing development processes and notations such as Object-Oriented Analysis and Design (OOAD), Enterprise Architecture (EA) frameworks, and Business Process Modeling (BPM) only cover part of what is required to support the architectural patterns currently emerging under the SOA umbrella. Thus, there is a need for an enhanced, interdisciplinary service modeling approach.
Today's Web services implementations are typically simple and often similar to a client-server model. However, platform-neutral interchange is supported, which allows a diverse range of client implementations to interact with new or legacy code as server functions. Much has been written about the technologies that make such applications straightforward to implement. It is now time to look at the bigger picture of what we can do with them. The author addresses the question of how to move forward from simple models to those that represent real-world business models of arbitrary complexity.
Pat Helland of Microsoft Corporation explores the idea that information technology is evolving in a fashion similar to how American cities have evolved over the last two centuries. The opportunities and pressures of the technological revolution have driven our metropolises to adopt new frameworks, models, and patterns for commerce and communication. Recent developments in IT are analogous. What can we learn about the present and future directions of IT by studying the recent history of our urban centers? (10 printed pages) (Microsoft Architect Journal)
Standards-based messaging allows flexible integration without having to roll out an enterprise-wide services architecture.
The Patterns for e-business are a group of proven, reusable assets that can be used to increase the speed of developing and deploying Web applications. This redbook focuses how the Self-Service and Extended Enterprise business patterns, and the Application Integration pattern, can be used to start implementing solutions using the service oriented architecture approach.
Time and time again we hear the same message - that technology issues are generally relatively easy to resolve. In contrast resolving people and process matters generally takes more than mere rocket science.
The IT Impedance Mismatch is how ZapThink Founder and Senior Analyst Ronald Schmelzer describes the frequent gulfs between IT implementations and their original business requirements. At the same time, IONA Technologies' Chief Engineer of Product Innovation Steve Vinoski sees a Web Services Gap forestalling a possible solution.
This is the first in a series of papers intended to help you better understand the value of a service-oriented architecture (SOA), and to develop a realistic plan for evaluating your current infrastructure and migrating it to a true service-oriented architecture.
This is an open letter to the vendor community, and/or the many excellent programmers who lost their jobs in the recent downturn. An opportunity awaits. We are at the cusp of making service oriented architectures a reality thanks to the hype about and interest in Web services. Companies are actually embracing the concept and moving forward. But they need to be able to purchase services that will plug into their architectures, and are finding few suitable solutions out there to meet that need. Beth Gold-Bernstein, in ebizQ.
An introduction to the W3C's Web Services Architecture Working Group, and its role in defining a coherent architecture for the currently chaotic ecology of web services specifications.
ServiceOriented.org is a short but nononsense guide to SOE, SOA, GXA, and all the WS-* stuff.
This site will help you get started with Web services and service-oriented architectures. It features free articles, product listings, and services that can be used to develop a service-oriented architecture.
Michael Stevens begin a new series on an architecture made up of components and interconnections that stress interoperability and location transparency -- a foundation for the new Web services model.
Discover what benefits you will reap by adding a service layer in the early stages of a project. You will gain a better return on your investment, flexibility with code mobility, enhanced security and other key benefits by implementing service-oriented architecture!
W3C Working Draft 14 November 2002. This document describes the Web Service Architecture. The Web services reference architecture identifies the functional components, defines the relationships among those components, and establishes a set of constraints upon each to effect the desired properties of the overall architecture.
Assembling on-demand web services to automate business, commerce, and the sharing of knowledge
Web Services Architecture Requirements W3C Working Draft 29 April 2002