Home > Service-Oriented Architecture
Service-Oriented Architecture
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
Enterprise Architecture, BPM, SOA and Master Data Management (MDM)http://entarch.blogspot.com/2008/08/enterprise-architecture-bpm-soa-and.html 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.- Business Process Management - Service-Oriented Architecture - Enterprise Architecture - |
1 vote
|
Testing Service-Oriented Architectures: A Primer for the Real Worldhttp://www.cio.com/article/print/440413 Matthew Heusser, July 31, 2008: How to test service-oriented architectures is no idle question. A failure in a SOA system at Heathrow Airport's $8.6 Billion Terminal 5 caused 1.6 British Pounds (about 3.2 million U.S. dollars) of losses in one week. The error? Simply that a filter put in to ensure that the baggage handler was tested in isolation was never removed - so event messages were never passed on to other, dependent systems.- Service-Oriented Architecture - |
|
Implementing Service Oriented Architecture at the Canada Institute for Scientific and Technical Informationhttp://ea.typepad.com/enterprise_abstraction/2008/07/my-paper---implementing-soa-at-cisti.html 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.- Service-Oriented Architecture - Enterprise Architecture - |
|
Businesses aren't machines, and enterprise architecture can't make them sohttp://www.ebizq.net/blogs/softwareinfrastructure/2008/07/businesses_arent_machines_and.php 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.- Service-Oriented Architecture - Enterprise Architecture - |
|
The Open Group's SOA ontologyhttp://www.opengroup.org/projects/soa-ontology/doc.tpl?gdid=16940 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.- OWL - Service-Oriented Architecture - |
|
About SOA at SAPhttps://www.sdn.sap.com/irj/sdn/weblogs?blog=/pub/wlg/10144 Stephan de Haas: In a nutshell, SAP's SOA Middleware and Application Infrastructure is promising. SAP has a very advanced business process platform providing Enterprise Services upon which clients can leverage the benefits of SOA to create the 20% of innovative processes, also integrating non-SAP applications, to increase their market share. Furthermore, SAP's process platform and its approach to co-innovation is positive, inceasing the opportunity for customers to source further innovative processes from ISVs that deliver on SAP's platform. The integrated portfolio minimizes complexities and help to run the remaining 80% of standard processes most efficiently. Last but not least, SAP offers a evolutionary migration path to Enterprise SOA for customers.- Service-Oriented Architecture - |
1 vote
|
When SOAs rule the worldhttp://www.networkworld.com/supp/2005/ndc1/022105qa.html Author Geoffrey Moore explains how SOAs will become the underlying force of the new data center.- Service-Oriented Architecture - |
|
RESTful SOA using XMLhttp://www.ibm.com/developerworks/library/x-restfulsoa/ Service Oriented Architecture usually implies heavyweight technology for large enterprises. The advantages of the SOA architectural pattern also apply to smaller environments. To follow SOA principles, you don't necessarily need all the overhead that is useful in larger environments. You can use lightweight principles like REST to do so. This article describes how.- REST - Service-Oriented Architecture - |
|
SOA spend up despite unclear benefitshttp://www.infoworld.com/article/08/02/25/news-soa-adoption_1.html The number of companies investing in service-oriented architecture (SOA) has doubled over the past year in every part of the world, with a typical annual spend of nearly $1.4 million, according to a new research report from the analyst firm AMR Research that surveyed 405 companies in the U.S., Germany and China.- Service-Oriented Architecture - |
|
Villages, Cities and Whether SOA Is Hype?http://thestewscope.wordpress.com/2008/02/18/villages-cities-and-whether-soa-is-hype/ 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 - Enterprise Architecture - |
|
Exploring the fundamentals of architecture and services in an SOA: Part 3: Service-oriented solutions and enterprise architecturehttp://www.ibm.com/developerworks/library/ar-archserv3/index.html In this article we look at what makes an IT solution service-oriented. We find out what this looks like in the deployment and runtime views, and talk about various important aspects to taking an enterprise view to SOA. Draws on CBM, Component Business Modeling, in using business components in a business architecture map.- Service-Oriented Architecture - Enterprise Architecture - |
|
SOA's Perfect Mate?http://www.informationweek.com/management/showArticle.jhtml?articleID=206100656 Virtualization 2.0 will go beyond server consolidation, making applications more agile and scalable to fit a service-oriented architecture. They're two of today's hottest technologies, and for good reason. Server virtualization provides cost savings on top of flexibility, while a service-oriented architecture affords application reuse and fast response to business needs. But the benefits of combining them can be less obvious. SOA helps with virtualization by breaking applications into smaller chunks that are more easily spread across multiple servers or CPUs, even off-loaded to outside service providers. Through common runtimes like Java and XML standards, SOA shields APIs from the underlying hardware or operating system. In return, virtualization simplifies SOA by easing provisioning of new hardware resources. By Andy Dornan, InformationWeek, February 2, 2008- Service-Oriented Architecture - |
|
B Margolis (2007)
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.
|
|
Nicolai M. Josuttis (2007)
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.
|
2 votes
|
Paul C. Brown (2007)
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.
|
1 vote
|
Dan Woods, Thomas Mattern (2006)
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.
|
|
Service-Oriented Architecture and Enterprise Architecture, Part 3: How do they work together?http://www.ibm.com/developerworks/webservices/library/ws-soa-enterprise3/index.html Dr. Mamdouh Ibrahim, Gil Long. IBM developerWorks, 30 August 2007. If you're adopting a Service-Oriented Architecture (SOA) and developing an Enterprise Architecture (EA) simultaneously - or planning to - you'll benefit from this article. The first two parts in this series compared and contrasted SOA and EA and covered problems that can result from not coordinating EA and SOA activities within an enterprise. The authors came face to face with these issues while working on a US$1.6 billion client engagement where both SOA and EA were under development. In this final installment of the series, learn from their experience as they provide guidance to help you address these challenges, and hopefully avoid costly setbacks.- Enterprise Architecture - Service-Oriented Architecture - |
|
Sandy Carter (2007)
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.
|
1 vote
|
Dirk Krafzig, Karl Banke, Dirk Slama (2004)
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.
|
4 votes
|
Larstan Editors (2006)
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.
|
1 vote
|
Jason Bloomberg, Ronald Schmelzer (2006)
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.
|
4 votes
|
Paul Allen (2006)
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.
|
1 vote
|
Norbert Bieberstein, Sanjay Bose, Marc Fiammante, Keith Jones, Rawn Shah (2005)
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
|
|
Thomas Erl (2005)
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.
|
3 votes
|
A Mulholland, C, S Thomas, P Kurchina (2007)
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.
|
3 votes
|
