Service-Oriented Architecture
Related tags:
Digital Identity
:: Document Formats
:: Enterprise Architecture
:: Enterprise Service Bus
:: Information Architecture
:: Interoperability
:: Open Standards
:: Service Component Architecture
:: SOA Reference Models
:: Standards
:: Web Services
:: XML
Links
Sold on SOAComputerworld's Executive Bulletin, "Sold on SOA," sponsored by Fujitsu, explains why CIOs are excited about service-oriented architectures, which have the potential to reduce IT costs, improve business and IT agility, increase software asset reuse, orchestrate business processes based on reusable "services," and ultimately replace the proprietary IT integration model that proliferated in the 1990s with a lower-cost, standards-based SOA approach to enterprise integration. The report also details the challenges that CIOs face in completing a successful implementation. For example, SOA is an IT discipline that requires proper strategy and planning, a new governance model that involves the IT and business organization, a new architecture model and development process, and new technology solutions to be able to realize these potential benefits. After providing an overview of business, technical and cultural issues that must be addressed, the report provides hands-on strategies and successful case studies to help make your project a success.- Service-Oriented Architecture - |
|
Event Processing (CEP) - The Role of Event Processing in Modern Businesshttp://www.ebizq.net/hot_topics/cep/features/8303.html?page=1 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.- Business Process Management - Enterprise Architecture - Service-Oriented Architecture - |
|
The awkward dance between BPM and SOAhttp://blogs.zdnet.com/service-oriented/?p=928 Joe McKendrick: Does business process management (BPM) need SOA to go forward? Does SOA need BPM to be relevant? Are they one in the same? Or are they completely different animals? Depending upon whom you read, BPM is either worlds apart from SOA, or the two are fused right down to the genetic level.- Business Process Management - Service-Oriented Architecture - |
|
Eric A. Marks, Michael Bell (2006)
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.
|
|
SOA in the Real WorldMicrosoft ebook, July 2007. SOA is an architectural approach to creating systems built from autonomous services. With SOA, integration becomes forethought rather than afterthought.This book introduces a set of architectural capabilities, and explores them in subsequent chapters.- Service-Oriented Architecture - |
|
The Merging of SOA and Web 2.0http://www.eweek.com/article2/0,1895,2158558,00.asp 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.- Service-Oriented Architecture - Web 2.0 - |
|
Pragmatic SOA Interoperabilityhttp://soa.sys-con.com/read/393668.htm 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.- Interoperability - Service-Oriented Architecture - |
|
Are You Ready for Mashups?http://soa.sys-con.com/read/393667.htm 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!- Service-Oriented Architecture - Web 2.0 - |
|
Enterprise SOA Adoption Strategieshttp://www.infoq.com/minibooks/enterprise-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.- Service-Oriented Architecture - |
|
How To Navigate A Sea of SOA Standardshttp://www.cio.com/article/104007/How_To_Navigate_A_Sea_of_SOA_Standards 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.- Service-Oriented Architecture - Standards - |
|
Using enterprise architecture framework to map services and set their granularityhttp://www.theeagroup.net/ea/Default.aspx?tabid=39&mid=357&ctl=Details&ItemID=7 Natty Gur, SAP: Enterprise architecture framework is used to carry on enterprise architecture work for enterprises. Enterprise architecture helps enterprises to deal with today challenges such as low and regulation compliance, agility of the business and the IT, managing portfolio, making the CEO vision into reality and others. Dealing with business and IT agility touches SOA and services. In this article we?ll see how we can use architecture framework to map enterprise level services and set their granularity.- Service-Oriented Architecture - Enterprise Architecture - |
|
SCA V1.0 Publication and OASIS Standardization Intent Announcementhttp://osoa.org/pages/viewpage.action?pageId=4178 Open SOA Collaboration Chooses OASIS to Advance SCA and SDO Specifications. March 21, 2007 - Eighteen leading technology vendors focused on driving technology initiatives supporting the creation of industry standards around service oriented architectures (SOA), today announced that key Service Component Architecture (SCA) and Service Data Objects (SDO) specifications have completed incubation and will be formally submitted to OASIS for advancement through its open standards process. The SCA specifications are designed to help simplify the creation and composition of services, critical to building applications using services based on an SOA approach. With these SCA specifications now mature, the partners intend to turn over their standardization process to OASIS. Additionally, the partners have completed work on the SDO specifications, designed to enable uniform access to data residing in multiple locations and formats, and will turn over stewardship of SDO/Java work to the Java Community Process and non-Java (C++) work to OASIS.- Service Component Architecture - Service-Oriented Architecture - |
|
Teaming up for SOAhttp://www.infoworld.com/article/07/03/05/10FEcollabgov_1.html By Phillip J. Windley: Governance policies chiseled in stone aren't SOA, they're DOA. Here's how to keep governance collaborative and effective.- IT Governance - Service-Oriented Architecture - |
|
Eleven Emerging Ideas for SOA Architects in 2007http://hinchcliffe.org/archive/2007/01/20/12675.aspx Dion Hinchcliffe: As I highlighted recently on ZDNet, 48% of CIOs will be looking to actually start using their SOAs to connect to external partners this year. Unfortunately, we've been building landscapes of Web services for quite a few years now and for many, the tipping point for SOA adoption seems as elusive as ever. While trying to understand why this is, one common explanation I offer is that the A in SOA is often missing. When you ask server-side developers in a given organization what they are developing, they usually say Web services. When you talk to architects in the same organization, they usually say they are building SOAs.- Service-Oriented Architecture - |
|
Is Your Enterprise Architecture Healthy?http://webservices.sys-con.com/read/329863.htm 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.- Service-Oriented Architecture - Enterprise Architecture - |
|
Web Services Specifications and SOA Interoperabilityhttp://opensource.sys-con.com/read/314083.htm 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 - WS-specs - |
|
The Lego Model of SOAhttp://www.zapthink.com/report.html?id=ZAPFLASH-20061212 ZapFlash by Jason Bloomberg. Any attempt to explain Service-Oriented Architecture (SOA) to a business audience typically elicits one of two standard responses: "this is techie stuff; you should talk to my IT people" or even worse, "I don't see the business value." The irony, of course, is that Service Orientation is a business approach for leveraging IT capabilities as business resources to meet the changing needs of the business in agile, cost-effective ways, and is thus critically relevant to today's business. But taking all the admittedly technical benefits of SOA, including loose coupling, composability, and reusability, and placing them in a sufficiently explanatory business context has always been a difficult challenge.- Service-Oriented Architecture - |
|
Best Practices for Building SOA Applicationshttp://ajax.sys-con.com/read/275111.htm 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 governance and the prevention of service-oriented anarchyhttp://www-128.ibm.com/developerworks/websphere/techjournal/0609_col_simmons/0609_col_simmons.html Success with SOA, at an enterprise level, mandates adoption of a robust and disciplined governance framework. Although organizations may differ on the specific functions enabled within their governance model, a common set of capabilities needs to be addressed for SOA. This column discusses the need to build effective governance frameworks while examining customer examples.- Service-Oriented Architecture - IT Governance - |
|
10-step program to SOA successhttp://news.zdnet.com/2100-3513_22-6108621.html One of the best parts of my job is meeting with people to discuss their technology initiatives. In the past couple of years alone, I have traveled around the world several times and met with thousands of people at public SOA forums and in private gatherings. This group consists of architects, developers, project leaders and CIOs--and they are at varying stages of adopting SOA, from just dipping their toes in the pool to full scale implementation. The most rewarding thing for me is when I get a chance to engage in and facilitate a conversation with a room of people that includes those who have successfully completed SOA projects. Listening to these "pioneers" share their experiences, both positive and negative, with those still trying to figure out SOAs is an eye-opening experience. Across all of these situations, and there have been many, I have noted a consistent set of themes which I have rolled up into what I will call the 10-step program to SOA success.- Service-Oriented Architecture - |
|
Managing SOX in the Age of SOAhttp://webservices.sys-con.com/read/250507.htm 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.- Service-Oriented Architecture - Management - |
|
Finally - a standard for Service Oriented Architecture (SOA)http://technoracle.blogspot.com/2006/07/finally-standard-for-service-oriented.html 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.- Service-Oriented Architecture - SOA Reference Models - |
|
Open SOA CollaborationThe Open SOA Collaboration represents an informal alliance of industry leaders that share a common interest: defining a language-neutral programming model that meets the needs of enterprise developers who are developing software that exploits Service Oriented Architecture characteristics and benefits. The Collaboration is not a Standards Body; it is an alliance who wish to innovate rapidly in the development of this programming model and to deliver Specifications to the community for implementation. These specifications are made available to the community on a Royalty Free basis for the creation of compatible implementations. When mature, the intent is to hand these specifications over to a suitable Standards Body for future shepherding. The Open Service Oriented Architecture collaboration is currently working on a series of specifications that are made available to the industry on a Royalty Free licensing basis. This site is the focal point both for completed specifications, and for early draft specifications where we seek community feedback. The Industry Partners are currently working on two main projects: Service Component Architecture (SCA) and Service Data Objects (SDO). Service Component Architecture aims to provide a model for the creation of service components in a wide range of languages and a model for assembling service components into a business solution - activities which are at the heart of building applications using a service-oriented architecture. Service Data Objects aims to provide consistent means of handling data within applications, whatever its source or format may be. SDO provides a way of unifying data handling for databases and for services. SDO also has mechanisms for the handling of data while detached from its source.- Service Component Architecture - Service-Oriented Architecture - |
|
Service Versioning For SOAhttp://webservices.sys-con.com/read/250503.htm (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- Web Services - Service-Oriented Architecture - |
|
Readings in Service OrientationMany 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.- Service-Oriented Architecture - |
|
