

Mehr erfahren
Den Autoren folgen
Alle ansehenOK
Enterprise SOA: Service-Oriented Architecture Best Practices (The Coad Series) (Englisch) Taschenbuch – Illustriert, 9. November 2004
Dirk Krafzig
(Autor)
Finden Sie alle Bücher, Informationen zum Autor
und mehr.
Siehe Suchergebnisse für diesen Autor
Sind Sie ein Autor?
Erfahren Sie mehr über Author Central
|
Karl Banke
(Mitwirkende)
Finden Sie alle Bücher, Informationen zum Autor
und mehr.
Siehe Suchergebnisse für diesen Autor
Sind Sie ein Autor?
Erfahren Sie mehr über Author Central
|
Dirk Slama
(Mitwirkende)
Finden Sie alle Bücher, Informationen zum Autor
und mehr.
Siehe Suchergebnisse für diesen Autor
Sind Sie ein Autor?
Erfahren Sie mehr über Author Central
|
Bestellung innerhalb 17 Stdn. und 12 Min. Siehe Details.
-
Seitenzahl der Print-Ausgabe418 Seiten
-
SpracheEnglisch
-
HerausgeberPrentice Hall
-
Erscheinungstermin9. November 2004
-
Abmessungen17.6 x 2.41 x 22.81 cm
-
ISBN-100131465759
-
ISBN-13978-0131465756
Ich möchte dieses Buch auf dem Kindle lesen.
Sie haben keinen Kindle? Hier kaufen oder eine gratis Kindle Lese-App herunterladen.
Produktinformation
- Herausgeber : Prentice Hall; Illustrated Edition (9. November 2004)
- Sprache : Englisch
- Taschenbuch : 418 Seiten
- ISBN-10 : 0131465759
- ISBN-13 : 978-0131465756
- Abmessungen : 17.6 x 2.41 x 22.81 cm
-
Amazon Bestseller-Rang:
Nr. 1,552,770 in Bücher (Siehe Top 100 in Bücher)
- Nr. 1,530 in Computernetzwerke
- Nr. 3,167 in Netzwerke
- Nr. 89,728 in Ingenieurwissenschaft & Technik (Bücher)
- Kundenrezensionen:
Produktbeschreibungen
Synopsis
Buchrückseite
"By delivering SAP's next-generation applications based on a Services-Oriented Architecture, SAP is at the forefront of making Web services work for the enterprise. The Enterprise Services Architecture enables unprecedented flexibility in business process deployment, allowing companies to execute and innovate end-to-end processes across departments and companies, with minimum disruption to other systems and existing IT investments. This strategy comes to life with SAP NetWeaver, which is the technological foundation of the Enterprise Services Architecture. It provides easy integration of people, information, and systems in heterogeneous IT environments and provides a future proof application platform. Enterprise SOA provides readers with the architectural blueprints and SOA-driven project management strategies that are required to successfully adopt SOA on an enterprise level."
Dr. Peter Graf, SVP Product Marketing, SAP
The SOA principles outlined in this book enable enterprises to leverage robust and proven middleware platforms, including CORBA, to build flexible and business-oriented service architectures. The authors also clearly describe the right strategies for using Model Driven Architecture (MDA) to manage SOA Service Repositories in a platform-independent way, enabling enterprises to better address the problem of heterogeneity at many levels. The Object Management Group was created just to address this central problem of integration in the face of constantly changing heterogeneity and platform churn, so I strongly recommend this book for the bookshelf of every enterprise architect and developer.
Richard Mark Soley, Ph.D. chairman and chief executive officer, Object Management Group, Inc.
Enterprise SOA provides strategies that help large enterprises to increase the agility of their IT systemsone of the most pressing issues of contemporary IT. Covering both a business and architectural view, these strategies aim to promote the implementation of an IT infrastructure that can serve as a base for the development of truly flexible business processes. This book covers its subject with great profoundness based on real world evidence. It is in the interest of everybody involved with software architectureparticularly for anybody who intends to establish a Service-Oriented Architectureto read this book.
Dr. Helge Heß, director Business Process Management, IDS Scheer AG
"...The SOA principles described in this book are the foundation on which enterprises can build an IT architecture that will satisfy today's most important IT requirementsagility and flexibilityat affordable costs..."
Martin Frick, Head of IT, Winterthur Group
Providing the roadmap for delivering on the promise of Service-Oriented Architecture
Enterprise SOA presents a complete roadmap for leveraging the principles of Service-Oriented Architectures to reduce cost and risk, improve efficiency and agility, and liberate your organization from the vagaries of changing technology.
- Benefit from the lessons of four enterprise-level SOA case studies from Credit Suisse, Halifax Bank of Scotland, and other world-class enterprises
- Make your business technology independent and manage infrastructure heterogeneity by focusing on architecture, not specific implementation techniques
- Recognize the technical and nontechnical success factors for SOA in the enterprise
- Define and communicate the economic value proposition of an SOA
- Apply pragmatic design principles to solve the problems of data and process integrity in an SOA environment
Whether you're a manager, architect, analyst, or developer, if you must drive greater value from IT services, Enterprise SOA will show you howfrom start to finish.
About the AuthorsDIRK KRAFZIG, KARL BANKE, and DIRK SLAMA have many years of experience in enterprise IT, including project management and distributed system design for large-scale projects. This book subsumes the knowledge of Service-Oriented Architectures that they have acquired since 1998, when they made their first steps toward this new architecture paradigm.
About the Web SiteWeb site www.enterprise-soa.com, provides a variety of supplemental material, including: articles, examples, and additional case studies.
© Copyright Pearson Education. All rights reserved.
Über den Autor und weitere Mitwirkende
About the Authors Dirk Krafzig
Dirk has been dealing with the challenges of enterprise IT and distributed software architectures throughout his entire working life. He devoted himself to SOA in 2001 when he joined Shinka Technologies, a start-up company and platform vendor in the early days of XML-based Web services. Since then, Dirk has acquired a rich set of real world experience with this upcoming new paradigm both from the view point of a platform vendor and from the perspective of software projects in different industry verticals.
Writing this book was an issue of personal concern to him as it provided the opportunity to share his experiences and many insights into the nature of enterprise IT with his readers.
Today, Dirk is designing enterprise applications and managing projects, applying the guiding principles outlined in this book. Dirk has a Ph.D. in Natural Science and an MSc in Computer Science. He lives in Düsseldorf, Germany, and is 39 years old, married, and the father of two children.
Karl BankeSoftware architecture has been with Karl since he programmed his first TRON-like game on the then state-of-the art ZX81 in the early 1980s. After graduating as a Master of Physics, he gained his commercial experience in various consulting assignments, mostly in the financial and telecommunications sector.
He moved through stages of consultant, technical lead, software architect, and project manager using a variety of object-oriented technologies, programming languages, and distributed computing environments. Soon realizing that he was too constrained as an employee in doing what he thought necessary in software development, he co-founded the company iternum in 2000, where he currently acts as a principal consultant and general manager.
Karl permanently lives in Mainz, Germany when not temporarily relocated by a current project.
Dirk SlamaHaving spent the last ten years at the forefront of distributed computing technology, Dirk has developed an in-depth understanding of enterprise software architectures and their application in a variety of industry verticals. Dirk was a senior consultant with IONA Technologies, working with Fortune 500 customers in Europe, America, and Asia on large-scale software integration projects. After this, Dirk set up his own company, Shinka Technologies, which successfully developed one of the first XML-based Web services middleware products, starting as early as 1999.
Dirk holds an MSc in computer sciences from TU-Berlin and an MBA from IMD in Lausanne. He is a co-author of Enterprise CORBA (Prentice Hall, 1999), the leading book on CORBA-based system architectures. Dirk is currently working as a solution architect for Computer Sciences Corporation in Zurich, Switzerland.
Contact: authors@enterprise-soa.com
Prolog. Abdruck erfolgt mit freundlicher Genehmigung der Rechteinhaber. Alle Rechte vorbehalten.
Foreword
At the turn of the nineteenth century, a wave of new technologies such as the steam engine, electricity, the loom, the railway, and the telephone emerged. Urbanization and the mass production of goods in large factories fundamentally changed how mankind lived and worked together.
One hundred years later, the industrial revolution had not slowed down: At the turn of the twentieth century, automation, specialization, and a never-ending spiral of efficiency improvement have resulted in modern economies with unheard-of industrial productivity.
After a phase of consolidation during the transition from the twentieth to the twenty-first century, globalization and virtualization have now become the key drivers of our economic lives. Without a doubt, they will yet again change how we live and work together.
If we take a closer look at the past 20 years, we can observe that established business rules have been constantly redefined. New business models emerged; small companies quickly grew into billion-dollar multinationals, aggressively attacking other established companies. A wave of mergers, acquisitions, and buyouts changed the overall industrial landscape.
IT has played a major role in all of this, be it through controlling production processes and supply chains or by creating real-time links between financial markets, thus virtually eliminating arbitrage opportunities by closing the time gaps of trading around the globe. The Internet boom and the "virtual enterprise" are cornerstones of this ongoing development. Entirely new products and services have been created, which would have been unthinkable without the support of modern IT.
Without a doubt, today's modern enterprises are completely dependent on their IT. Consequently, today's IT is driven by the same dynamics as the enterprise itself. Today, we expect an extremely high level of flexibility and agility from our enterprise IT. During the post Internet-boom years, cost efficiency quickly became another key requirement, if not the most important one.
Enterprise IT has changed as a result of the constantly increasing pressure. In the early days of enterprise computing, IT was merely responsible for providing storage and processing capacity, with more and more business logic being added throughout the decades. During the different boom phases in the 1980s and 1990s, a plethora of new applications emerged, often side by side with the information silos that had been developed in the previous 20 years.
Today, the increasing cost pressure is forcing us to efficiently reuse existing systems while also developing new functionality and constantly adapting to changing business requirements. The term "legacy system" is now often replaced with "heritage system" in order to emphasize the value that lies in the existing systems.
The increases in reuse and harmonization requirements have been fueled by the urgency of integrating the historically grown IT landscapes in order to improve IT efficiency and agility. As a result, we could observe at a technical level the emergence of middleware tools and Enterprise Application Integration (EAI) platforms in what can be seen as a post-RDBMS phase.
While a lot of trial-and-error projects were executed in the 1990s, with more or less high levels of success, the development of EAI and middleware concepts has now been culminated in the principles of Service-Oriented Architecture (SOA), which can be seen as an important evolutionary point in the development of integration technologies.
What is important about SOA is that it has taken away the focus from fine-grained, technology-oriented entities such as database rows or Java objects, focusing instead on business-centric services with business-level transaction granularity. Furthermore, SOA is not an enterprise technology standard, meaning it is not dependent on a single technical protocol such as IIOP or SOAP. Instead, it represents an architectural blueprint, which can incorporate many different technologies and does not require specific protocols or bridging technologies. The focus is on defining cleanly cut service contracts with a clear business orientation.
At the Winterthur, as in any other large company, we have been facing all of the preceding issues of historically grown systems and information silos. We had to find a solution to increase our IT efficiency and agility. The Winterthur, with approximately 20,000 employees worldwide and over 130 billion Swiss franks of assets being managed (as of December 31, 2003), is a leading Swiss insurance company. As is the case with any well-organized company, we rely on our IT infrastructure to manage assets, products, processes, customers, partners, employees, and any other aspect of business life.
Our core business systems are based on highly reliable mainframe computers that we invested in over the past decades. However, like most other enterprises relying on mainframes for their back-end systems, we saw the increasing need over the years to open up these back-end systems. The main reason for this was to enable reuse of the core business logic and data on these systems for new Internet and intranet front-end systems on nonmainframe platforms such as UNIX and Windows.
To facilitate this development, we built up an application and integration platform, which laid the technical basis for Winterthur's SOA. While the initial development started off at our core Swiss market unit, the platform is nowadays reused abroad, because of its success and the prevailing analogous technical requirements of other market units. Thus, we create the basis to realize synergies and enhance our international initiatives.
Building on our technical platform, combined with our in-house experience in the area of SOA and with the experience that our holding company Credit Suisse Group has gathered in similar re-architectural efforts, we have been extremely successful. The Winterthur SOA has achieved the goal of opening up our back-end systems in new application development areas on other platforms. A solid SOA-based architectural approach is at the heart of our IT strategy.
This book is important because it provides enterprise architects with a roadmap for the successful establishment of SOA at the enterprise level. While a lot of the underlying principles of the original Winterthur SOA have had to be derived from past experience and intuition due to lack of SOA literature at the time, this book provides a concrete guide, blueprints, and best practices for SOA architects. In addition to the Winterthur case study in chapter 15, you will find many more concrete examples of how large corporations have started to adopt the principles of SOA in their IT architectures.
It is also very important that this book not only focuses on the technical aspects of SOA, but also places strong emphasis on the delicate issues of establishing SOA at the enterprise level, truly deserving the title Enterprise SOA.
The SOA principles described in this book are the foundation on which enterprises can build an IT architecture that will satisfy today's most important IT requirementsagility and flexibilityat affordable costs.
Martin Frick, Head of IT at the Winterthur Group
© Copyright Pearson Education. All rights reserved.
Kundenrezensionen
Spitzenbewertungen aus Deutschland
Derzeit tritt ein Problem beim Filtern der Rezensionen auf. Bitte versuchen Sie es später noch einmal.
Man merkt, dass das Buch auf langjähriger Erfahrung der Autoren aus "echten" IT-Projekten beruht. Erfrischend zu lesen, manchmal zum schmunzeln und immer sehr lehrreich und Praxis-relevant. Am besten hat mir die Darstellung der zahlreichen Case Studies gefallen, in denen erfolgreiche SOA Projekte darstellt werden.
Das Buch ist nicht nur für Software-Architekten sondern auch für Projektleiter und CIOs eine sehr empfehlenswerte Lektüre.
Dass dieses Buch ebenfalls von den Technikern in meinem Team gelesen und positiv beurteilt wird, stellt sich als großer Vorteil heraus. Zahlreiche Konzepte und Begriffsbildungen aus dem Buch erleichtern die tägliche Kommunikation miteinander (übrigens nicht nur für SOA Projekte nützlich!).
Spitzenrezensionen aus anderen Ländern

1) Covered a range of technologies, emphasizing that SOA is not just about throwing out a range of Web services.
2) Covered valid design/architecture choices, for example discussing asynchronous and synchronous approaches and where they might each be useful.
3) Discussed how services can be a valuable tool in bringing IT/business closer together.
4) The case studies were very interesting, I actually would have liked it if the book had more detail but what it did include was useful.
5) The coverage of governance had me nodding my head, even if you don't chose to apply SOA you'll need to know how ensure that people don't fall back into tactical decision making.
6) Covered how SOA can change your approach to project management.
Having said that one issue I had with the book was the emphasis on having basic services as the cornerstone of your SOA (basic services being essentially entity services). I'm hoping that in a future edition the authors will explore how SOA can be used in a manner that work hand in hand with DDD and I think this would mean re-evaluating whether reusable entity services are really a good idea.
However I have no problems recommending this book, its a great read.


まずSOAはEnterprise IT のAgility を復活させるためのキー・エレメントであるとしています。サービスの定義については、3つの異なったエリアがあることを示し、サービスの特性によって(なんと粒度ではなく)4タイプにクラス化できると主張していることは説得力があります。さらに、これらを配置するSOAレイヤー・アーキテクチャを定義しており、これはいわゆる3層アーキテクチャとは異なるとの指摘もアーキテクトとしてよく理解できます。サービスは多段でフラクタル性はあるものの、複雑にはせず疎結合化によるAgilityを確保するにはこのSOAレイヤリングの考え方で十分であると思われます。
いままであまり話題にされてこなかったSOAのプロセス・インテグリティ、非機能的要件(スケーラビリティやアベイラビリティ、SLAなど)の解説があり、現実性の確保に大きく貢献しています。日ごろから疑問であったEAIとSOAの違い、親和性、相互利用性も解説され現実的で評価できると考えます。
さらにエンタープライズの視点からSOAに特化したProject ManagementやITガバナンスの視点が必要であり、既存の各手法にSOA向きのルールを付加すべきと提案しておりエンタープライズ的な視野を強化させています。最後に4つのSOA事例とそれぞれのLesson Learned が示されています。
文章も難解ではなく、丁寧に著述されています。しかし不満もないわけではありません。たとえば、ESBに必要な機能の解説が少ないし、エンタープライズレベルのSOAのガバナンスを記述しているのであるからEAとの関連付けも解説がほしいと感じました。しかし、ITアーキテクトがいま読むべき旬の本であると思います。アメリカ発でない本でもあり、実践的なアーキテクトが元気になれる本です。

SIビジネスに関わっている職業柄、既知の内容がほとんどであったが、論理的有機的に体系化されており、考えをまとめる上で非常に有効だった。
SOAのモチベーションと要件、そして既存技術を用いていかに新たに開発したアプリケーションと既存のアセットを統合してゆくのか丁寧に記述している。ほぼ策定作業が終了したJAX-WSやJBIといった標準も重要であるが、異機種混交の自社システムのコンピタンスを高めるには、(やるやらないは別にして)MDAによる自社ソリューションも選択肢の一つになるのでは、と勇気付けられた。
英文ではあるが平易な表現が多く、読み進むことはそれほど苦にはならない。
SOAとは何か悩んでいる人、ベンダーの言うことだけを聞いてSOAとは何かわかったつもりになっている人、いずれの方々にもお勧めできる久々の良書です。

(1)必ずしも分かりやすくない。でも、発売当時、洋書店に並んでいるSOAの本の中では、一番、内容がある目次構成でした。(2)テクニカルな記述が現在では中途半端。そのかわり、カバーしている話題が広い。(3)事例の紹介は少し古いという印象です。しかし、事例をみると、日本が遅れているというか、これからSOAのビジネスが日本で広がるだろうことを期待させます。(4)SOAの実現型は結局、プロトコルアダプターの開発と、メッセージコレオグラファーのセットだろうと、という読後感。
Momentanes Problem beim Laden dieses Menüs.