Executive's Guide to Cloud Computing Review

Average Reviews:

(More customer reviews)Are you looking to buy Executive's Guide to Cloud Computing? Here is the right place to find the great deals. we can offer discounts of up to 90% on Executive's Guide to Cloud Computing. Check out the link below:

>> Click Here to See Compare Prices and Get the Best Offers

Executive's Guide to Cloud Computing ReviewI have utilized this text to help C-level executives better understand the terminology, concepts, and potential business strategies associated with cloud computing. After spending time with this text, line of business executives can more effectively and confidently evaluate competing outsourced service offerings and understand which can deliver compelling value in their unique business situations.Executive's Guide to Cloud Computing OverviewYour organization can save and thrive in the cloud with this first non-technical guide to cloud computing for business leaders
In less than a decade Google, Amazon, and Salesforce.com went from unknown ideas to powerhouse fixtures in the economic landscape; in even less time offerings such as Linkedin, Youtube, Facebook, Twitter and many others also carved out important roles; in less than five years Apple's iTunes became the largest music retailer in North America.
They all share one key strategic decision – each of these organizations chose to harness the power of cloud computing to power their drives to dominance. With roots in supercomputing and many other technical disciplines, cloud computing is ushering in an entirely new economic reality – technology-enabled enterprises built on low cost, flexible, and limitless technical infrastructures.
The Executive's Guide to Cloud Computing reveals how you can apply the power of cloud computing throughout your enterprise, giving members of the C-suite a detailed look at:
Why cloud computing must be a top priority on your company's IT roadmaps
How the drive for scale, lower costs and greater agility is making cloud computing a fiscal and technological imperative
The relationship between cloud computing and other relevant IT initiatives
The strategic implications of cloud computing for the enterprise
Where to begin and how to get started integrating cloud computing into your existing operations

Now you can harness cloud computing's potential for your organization. Executive's Guide to Cloud Computing shows you how.

Want to learn more information about Executive's Guide to Cloud Computing?

>> Click Here to See All Customer Reviews & Ratings Now

Read More...

SOA-Based Enterprise Integration: A Step-by-Step Guide to Services-based Application Review

Average Reviews:

(More customer reviews)Are you looking to buy SOA-Based Enterprise Integration: A Step-by-Step Guide to Services-based Application? Here is the right place to find the great deals. we can offer discounts of up to 90% on SOA-Based Enterprise Integration: A Step-by-Step Guide to Services-based Application. Check out the link below:

>> Click Here to See Compare Prices and Get the Best Offers

SOA-Based Enterprise Integration: A Step-by-Step Guide to Services-based Application ReviewWhen I first looked at this book (after opening the package from Amazon), I thought it would be perfect... it's not a hefty 1000-page cookbook... and seemed like it would be just the perfect level of detail to rein in the broad topics into something coherent. In fact, the book does a decent job with the overall picture, but has some major flaws in style, presentation, and bias that renders it a groggy, often un-informing, experience. I stuck with it, because I had no alternative at hand, and a tight timeframe, so I can speak as a reviewer that has actually read the book.
The Good: This book contains a decent overview of SOA components and does tie them together in a good overall picture.
The Bad (part I): This book was written by an IBM Senior Architect. The technical editor for the book is an IBM Architect. The forward was written by an IBM Fellow. The back cover contains endorsements from two IBMers, one of which is the VP for WebSphere Marketing. Much of the book contains unbiased information on industry standards. However, much of the rest of the book is an over-the-top promotion of IBM products. For example, the capstone of this work is the chapter on Enterprise Service Bus. This chapter reads like glossy marketing literature for IBM products at best and like an informertial at worst. That chapter is only 30 pages long, but uses the word "WebSphere" 24 times by my count. Conversely, the non-IBM Weblogic is mentioned exactly 0 times in the same chapter, and rarely throughout the rest of the book. This book calls IBM's WESB "the prime example" of an application server based ESB and goes on to list, in bulletized form, its "features and advantages". In another section, the author states, "IBM offers the most complete product lines in this area."
The Bad (part II): This book is poorly presented. It can't decide if it is a 40,000 ft overview or a detailed description of various technologies. For example, SOAP is covered in 22 short pages. That's obviously not enough for anything more than an explanation of what it is, how it is used, why it's good, and a few examples. Yet the author tries to dive into the structure of a SOAP message to the point of who-cares detail for a book like this. In the 22 pages covering SOAP, for example, the author states FIVE TIMES that if the header element is present, it must precede the body element.
In addition, the author uses a highly verbose and repetitive style. It often seems that about 20% of the book is either telling you what it's going to tell you or telling you what it's already told you. The book could have contained the same amount of useful information in about 200 pages. This overly verbose and repetitive style gives the book a sense that the author, a PhD, does not know how to communicate effectively with lesser intellects and frequently overshoots his simplification. The result is that the work often, but inconsistently, reads a bit like a "for dummies" type of book.SOA-Based Enterprise Integration: A Step-by-Step Guide to Services-based Application Overview
Foreword by Ray Harishankar, IBM Fellow
"There are many books on the market on the topic of SOA and SOA's business and technology value.This book focuses on one of the key technical values of SOA and does an excellent job of describing SOA-based application integration by clarifying the relationship and patterns of SOA with other integration technologies in a distributed computing environment." Sandra Carter, IBM Vice President for SOA, BPM, and WebSphere Marketing
"Services Oriented Architectures present many challenges today in the integration of existing systems and new systems, along with many times, old legacy mainframe applications.This book successfully addresses many of the complexities we see in the integration of SOA and mainframe legacy applications, presenting options and approaches to integrate the applications with the rest of the enterprise.The author takes a clearly defined pattern-based approach discussing the advantages, tools and methods.Readers will benefit from the insights in this book whether they play the architect role or a developer role on a SOA project."Sue Miller-Sylvia, IBM Fellow and Application Development Service Area Leader

Want to learn more information about SOA-Based Enterprise Integration: A Step-by-Step Guide to Services-based Application?

>> Click Here to See All Customer Reviews & Ratings Now

Read More...

Web Service Contract Design and Versioning for SOA Review

Average Reviews:

(More customer reviews)Are you looking to buy Web Service Contract Design and Versioning for SOA? Here is the right place to find the great deals. we can offer discounts of up to 90% on Web Service Contract Design and Versioning for SOA. Check out the link below:

>> Click Here to See Compare Prices and Get the Best Offers

Web Service Contract Design and Versioning for SOA ReviewI just wanted to let other Kindle owners in the IT profession know that the content of this book is as good as the other reviews indicate, but you should buy the paper edition rather than the Kindle edition.
Most of the xml in the Kindle edition is unreadable, due to its being truncated at the left margin, and sometimes at the bottom of the page, as well. Some of the sidebar content has the same problem.
All in all, there's just too much content missing from the Kindle edition. With the hard copy being just ten dollars more, it's the better choice.Web Service Contract Design and Versioning for SOA OverviewThe Ultimate Guide for Designing and Governing Web Service ContractsFor Web services to succeed as part of SOA, they require balanced, effective technical contracts that enable services to be evolved and repeatedly reused for years to come. Now, a team of industry experts presents the first end-to-end guide to designing and governing Web service contracts. Writing for developers, architects, governance specialists, and other IT professionals, the authors cover the following areas:Understanding Web Service Contract Technologies Initial chapters and ongoing supplementary content help even the most inexperienced professional get up to speed on how all of the different technologies and design considerations relate to the creation of Web service contracts. For example, a visual anatomy of a Web service contract documented from logical and physical perspectives is provided, along with a chapter dedicated to describing namespaces in plain English. The book is further equipped with numerous case study examples and many illustrations.Fundamental and Advanced WSDLTutorial coverage of WSDL 1.1 and 2.0 and detailed descriptions of their differences is followed by numerous advanced WSDL topics and design techniques, including extreme loose coupling, modularization options, use of extensibility elements, asynchrony, message dispatch, service instance identification, non-SOAP HTTP binding, and WS-BPEL extensions. Also explained is how WSDL definitions are shaped by key SOA design patterns.Fundamental and Advanced XML SchemaXML Schema basics are covered within the context of Web services and SOA, after which advanced XML Schema chapters delve into a variety of specialized message design considerations and techniques, including the use of wildcards, reusability of schemas and schema fragments, type inheritance and composition, CRUD-style message design, and combining industry and custom schemas.Fundamental and Advanced WS-PolicyTopics, such as Policy Expression Structure, Composite Policies, Operator Composition Rules, and Policy Attachment establish a foundation upon which more advanced topics, such as policy reusability and centralization, nested, parameterized, and ignorable assertions are covered, along with an exploration of creating concurrent policy-enabled contracts and designing custom policy assertions and vocabularies.Fundamental Message Design with SOAPA broad range of message design-related topics are covered, including SOAP message structures, SOAP nodes and roles, SOAP faults, designing custom SOAP headers and working with industry-standard SOAP headers.Advanced Message Design with WS-AddressingThe art of message design is taken to a new level with in-depth descriptions of WS-Addressing endpoint references (EPRs) and MAP headers and an exploration of how they are applied via SOA design patterns. Also covered are WSDL binding considerations, related MEP rules, WS-Addressing policy assertions, and detailed coverage of how WS-Addressing relates to SOAP Action values.Advanced Message Design with MTOM, and SwADeveloping SOAP messages capable of transporting large documents or binary content is explored with a documentation of the MTOM packaging and serialization framework (including MTOM-related policy assertions), together with the SOAP with Attachments (SwA) standard and the related WS-I Attachments Profile.Versioning Techniques and StrategiesFundamental versioning theory starts off a series of chapters that dive into a variety of versioning techniques based on proven SOA design patterns including backward and forward compatibility, version identification strategies, service termination, policy versioning, validation by projection, concurrency control, partial understanding, and versioning with and without wildcards.Web Service Contracts and SOAThe constant focus of this book is on the design and versioning of Web service contracts in support of SOA and service-orientation. Relevant SOA design principles and design patterns are periodically discussed to demonstrate how specific Web service technologies can be applied and further optimized. Furthermore, several of the advanced chapters provide expert techniques for designing Web service contracts while taking SOA governance considerations into account.About the Web Siteswww.soabooks.com supplements this book with a variety of resources, including a diagram symbol legend, glossary, supplementary articles, and source code available for download.www.soaspecs.com provides further support by establishing a descriptive portal to XML and Web services specifications referenced in all of Erl's Service-Oriented Architecture books.

Want to learn more information about Web Service Contract Design and Versioning for SOA?

>> Click Here to See All Customer Reviews & Ratings Now

Read More...

Service-Oriented Modeling (SOA): Service Analysis, Design, and Architecture Review

Average Reviews:

(More customer reviews)Are you looking to buy Service-Oriented Modeling (SOA): Service Analysis, Design, and Architecture? Here is the right place to find the great deals. we can offer discounts of up to 90% on Service-Oriented Modeling (SOA): Service Analysis, Design, and Architecture. Check out the link below:

>> Click Here to See Compare Prices and Get the Best Offers

Service-Oriented Modeling (SOA): Service Analysis, Design, and Architecture ReviewI have purchased and read many SOA books and they have all fallen into one of 2 camps. They are usually either "HOW-TO" implement a SOAP/XML/WSDL based request response guides with the standard buzzwords of SOA Governance, WS-*Everything and the Kitchen Sink*, and of course a vague description of how an Enterprise Service Bus magically does away with years a poorly implemented legacy systems. This is the first SOA book that I have read that did not waste my time with page after page trivial XML examples but actually presented an entire working formal language(extended or inspired by the UML component model I believe) to describe your existing environment("As-Is") and future-state architecture in everday terms understandable by business users and application developers. I'll admit when I read that the approach is both 'Holistic' and 'Anthropomorphic' I felt like I was being marketed some Ginko-Biloba pseudo mysticism but as I read through I understood that this is an approach to SOA, probably the first, to actually make the the underlying services and consolidation of services visible and tanglible in the way an architect builds a scale model of a proposed structure to provide an in depth understanding of the project to those who are unable to turn equations into 3D structures in there heads(which is most of us). The authors crowning achievement, in my opinon, is the realization that everything (Legacy System, Schedule Batch Job, Business Apporval Process, Business Rules, Storage) must be treated as 'Services' is a quantum leap for SOA that moves the concept of SOA from a vague buzzword to a concrete deliverable, tangible item.Service-Oriented Modeling (SOA): Service Analysis, Design, and Architecture OverviewAnswers to your most pressing SOA development questionsHow do we start with service modeling? How do we analyze services for better reusability? Who should be involved? How do we create the best architecture model for our organization? This must-read for all enterprise leaders gives you all the answers and tools needed to develop a sound service-oriented architecture in your organization.Praise for Service-Oriented ModelingService Analysis, Design, and Architecture"Michael Bell has done it again with a book that will be remembered as a key facilitator of the global shift to Service-Oriented Architecture. . . . With this book, Michael Bell provides that foundation and more-an essential bible for the next generation of enterprise IT."-Eric Pulier, Executive Chairman, SOA Software"Michael Bell's insightful book provides common language and techniques for business and technology organizations to take advantage of the SOA paradigm. By focusing modeling techniques on the business problem, Bell provides a way for professionals to work throughout the life cycle to create reusable and enduring services."-Mike Zbranak, CIO, Chase Card Services"This book will become an imperative business and technology service-oriented modeling recipe for any manager, architect, modeler, analyst, and developer in today's software development industry."-Jeff Schneider, CEO, MomentumSI"'Innovative' and 'groundbreaking' are words that best describe Michael Bell's Service-Oriented Modeling. It depicts a true service modeling approach that elegantly closes a clear and critical service modeling gap in the SOA industry. This holistic book ties these concepts together using real-world examples across a service life cycle that transitions services from ideas and concepts into production assets that deliver business value. A must-read for business and technical SOA practitioners."-Eric A. Marks, CEO, AgilePath Corporation"As hot as SOA is today, many business and technology professionals still find it challenging to mind the gap between their disparate methodologies and objectives. Herein Michael Bell speaks clearly to both camps in straightforward language, outlining disciplines each can use to communicate effectively and advance the realization of corporate aims. This book is a bible for all who seek to drive business/technology into the future."-Mark Edward Goodrich, Director, Investing Product Management, Reuters Media"This book takes senior IT architects and systems designers into the depths of modeling for SOA, with a fresh new perspective on tools, terminology, and how to turn the theory into practice. His full life-cycle approach balances process, control, and accountability to align all the participants in the delivery pipeline-clearing the road for successful SOA business solutions."-Phil Gilligan, Chief Technology Officer, EBS

Want to learn more information about Service-Oriented Modeling (SOA): Service Analysis, Design, and Architecture?

>> Click Here to See All Customer Reviews & Ratings Now

Read More...

Security for Web Services and Service-Oriented Architectures Review

Average Reviews:

(More customer reviews)Are you looking to buy Security for Web Services and Service-Oriented Architectures? Here is the right place to find the great deals. we can offer discounts of up to 90% on Security for Web Services and Service-Oriented Architectures. Check out the link below:

>> Click Here to See Compare Prices and Get the Best Offers

Security for Web Services and Service-Oriented Architectures ReviewThe review is based only on the first three chapters that I have managed to read so far.
1. The premise of the book is pretty valuable. There is need for updated literature that takes web services security out of the standards world and makes it more approachable. On that count, I laud the initiative.
2. The book, however, suffers from several significant issues:
a. The proof-reading, for a book that purports to be a reference on the topic, is abysmal. Consider this snippet on page 35 related to threat modeling: "even though the security functions provided by the middleware are becoming more and more reach and complete,...". Any technical editor should have picked up the multiple mistakes in this sentence. Unfortunately, such mistakes abound in the book.
b. In trying to emphasize theory, the book often comes across as dry and irrelevant. For example, table 3.2 related to STRIDE Categories and the surrounding explanation on page 32, while being factually complete, seem like they belong to a Microsoft Press book. At the level the book aims for, what's important is not an explanation of STRIDE (why wouldn't I read Howard's or Swiderski's books for that?) but how that relates to Web services. Explaining the STRIDE concepts as related to a fictional Web Service might have been much more useful.
c.Some of the technical terms used in the book are downright incorrect. For example, on page 35, in the same paragraph as #2(a), the authors talk of "RBAC-based authorization mechanisms". RBAC itself stands for Role Based Access Control. What does it mean for an authorization mechanism to be RBAC-based?
d. If this book is to be useful at all, the figures need to be seriously improved. They are miniature, complex and hardly span a quarter of a page. In short, they are barely decipherable and there's a lot of text referring to such figures that becomes disconnected.
With all this said, I still give the book 3 stars because there is at least some method to the approach and it's much better than reading a bunch of W3C or OASIS standards. Not to mention the fact that chapter 3 refers to CAPEC that I had, in part, contributed attack patterns to :-)
I would definitely wish for the editors at Springer to take a serious look at the language and technical terminology and make figures more understandable. The book has a lot of promise and it would be a shame if such matters were to obscure that.Security for Web Services and Service-Oriented Architectures OverviewWeb services based on the eXtensible Markup Language (XML), the Simple Object Access Protocol (SOAP), and related standards, and deployed in Service-Oriented Architectures (SOA), are the key to Web-based interoperability for applications within and across organizations. It is crucial that the security of services and their interactions with users is ensured if Web services technology is to live up to its promise. However, the very features that make it attractive - such as greater and ubiquitous access to data and other resources, dynamic application configuration and reconfiguration through workflows, and relative autonomy - conflict with conventional security models and mechanisms.Elisa Bertino and her coauthors provide a comprehensive guide to security for Web services and SOA. They cover in detail all recent standards that address Web service security, including XML Encryption, XML Signature, WS-Security, and WS-SecureConversation, as well as recent research on access control for simple and conversation-based Web services, advanced digital identity management techniques, and access control for Web-based workflows. They explain how these implement means for identification, authentication, and authorization with respect to security aspects such as integrity, confidentiality, and availability.This book will serve practitioners as a comprehensive critical reference on Web service standards, with illustrative examples and analyses of critical issues; researchers will use it as a state-of-the-art overview of ongoing research and innovative new directions; and graduate students will use it as a textbook on advanced topics in computer and system security.

Want to learn more information about Security for Web Services and Service-Oriented Architectures?

>> Click Here to See All Customer Reviews & Ratings Now

Read More...

Modeling & Simulation-Based Data Engineering: Introducing Pragmatics into Ontologies for Net-Centric Information Exchange Review

Average Reviews:

(More customer reviews)Are you looking to buy Modeling & Simulation-Based Data Engineering: Introducing Pragmatics into Ontologies for Net-Centric Information Exchange? Here is the right place to find the great deals. we can offer discounts of up to 90% on Modeling & Simulation-Based Data Engineering: Introducing Pragmatics into Ontologies for Net-Centric Information Exchange. Check out the link below:

>> Click Here to See Compare Prices and Get the Best Offers

Modeling & Simulation-Based Data Engineering: Introducing Pragmatics into Ontologies for Net-Centric Information Exchange ReviewIt is often the case that a new area of inquiry, comprised of elements from seemingly disparate disciplines, yields surprising insights. Zeigler's and Hammonds's effort is no exception. While linguistics has from time to time informed mathematics and computer science, to my knowledge little has been done to date towards the application of semantics and pragmatics to this type of data exchange.
The prose is concise, clear, and conversational. Given the complexity of the two topics and the more or less mutual exclusivity of their lexicons, readers whose experience has been acquired only in the one or the other of these two disciplines will nevertheless quickly become comfortable in this discussion. The authors provide many examples to illustrate their line of reasoning, all drawn from a wide variety of sources.
As an IT professional with 15 years' experience and an advanced degree in a foreign language, I found this book satisfying, illuminating, and provocative. While it is intended to address a specific engineering problem, its implications extend well beyond its stated purview. Heartily recommended for those who would like to think about the synergies of data engineering and pragmatics, and also for those who want to think about what might be beyond the horizon.Modeling & Simulation-Based Data Engineering: Introducing Pragmatics into Ontologies for Net-Centric Information Exchange OverviewData Engineering has become a necessary and critical activity for business, engineering, and scientific organizations as the move to service oriented architecture and web services moves into full swing. Notably, the US Department of Defense is mandating that all of its agencies and contractors assume a defining presence on the Net-centric Global Information Grid. This book provides the first practical approach to data engineering and modeling, which supports interoperabililty with consumers of the data in a service- oriented architectures (SOAs). Although XML (eXtensible Modeling Language) is the lingua franca for such interoperability, it is not sufficient on its own. The approach in this book addresses critical objectives such as creating a single representation for multiple applications, designing models capable of supporting dynamic processes, and harmonizing legacy data models for web-based co-existence. The approach is based on the System Entity Structure (SES) which is a well-defined structure, methodology, and practical tool with all of the functionality of UML (Unified Modeling Language) and few of the drawbacks. The SES originated in the formal representation of hierarchical simulation models. So it provides an axiomatic formalism that enables automating the development of XML dtds and schemas, composition and decomposition of large data models, and analysis of commonality among structures.Zeigler and Hammond include a range of features to benefit their readers. Natural language, graphical and XML forms of SES specification are employed to allow mapping of legacy meta-data. Real world examples and case studies provide insight into data engineering and test evaluation in various application domains. Comparative information is provided on concepts of ontologies, modeling and simulation, introductory linguistic background, and support options enable programmers to work with advanced tools in the area. The website of the Arizona Center for Integrative Modeling and Simulation, co-founded by Zeigler in 2001, provides links to downloadable software to accompany the book.* The only practical guide to integrating XML and web services in data engineering* Introduces linguistic levels of interoperability for effective information exchange* Covers the interoperability standards mandated by national and international agencies * Complements Zeigler's classic THEORY OF MODELING AND SIMULATION

Want to learn more information about Modeling & Simulation-Based Data Engineering: Introducing Pragmatics into Ontologies for Net-Centric Information Exchange?

>> Click Here to See All Customer Reviews & Ratings Now

Read More...

Service-Oriented Architecture (SOA): Concepts, Technology, and Design Review

Average Reviews:

(More customer reviews)Are you looking to buy Service-Oriented Architecture (SOA): Concepts, Technology, and Design? Here is the right place to find the great deals. we can offer discounts of up to 90% on Service-Oriented Architecture (SOA): Concepts, Technology, and Design. Check out the link below:

>> Click Here to See Compare Prices and Get the Best Offers

Service-Oriented Architecture (SOA): Concepts, Technology, and Design ReviewThis book is superb. I have read every SOA book available (up until Apr/06) because it's part of my job as a technology research analyst and all-around techno-geek. From those that I have read and studied, this is the only one I feel compelled to write a review about. AND - because I did have to go through it in such detail I'm going to raid my research notes and share with you a detailed review of not just the book, but each of its chapters.
Chapter 1 - Introduction
Nothing special here, this is just a chapter that introduces the rest of the book. Call it a glorified table of contents if you will. At first I felt like skipping it altogether, but then I did what I'm supposed to do for my job and that is read each and every part. In the end, I'm glad I took the time for two reasons: By reading a summary of each of the chapters I got a good feel for what this book was going to cover and what it wasn't going to cover. Secondly, I liked the author's intro stuff about ideal and not so ideal (real) SOA. Kind of insightful and stinging at the same time. Still, though, this is still just a description of other chapters. It's also a chapter you can get for free at the book's web site.
Chapter 2 - Case Studies
Here the author provides background information for the two companies he uses as case studies. If you're into case studies, then you'll definitely want to read through this. But - I found the subsequent samples pretty easy to follow and I think you could get away with skipping this chapter if you really wanted to.
Chapter 3 - Introducing SOA
Here's where I started getting into the meat of the book. If you think you don't understand what soa is or what the industry's made of it or turned it into then you need to read this chapter. It breaks it all down and builds it all up again in a very systematic manner. Make sure you leave this chapter with an understanding of how primitive and contemporary variations of soa are different because the author uses these terms later.
Chapter4 - The Evolution of SOA
Finally someone who makes a distinction between specification and standard and gets it right. This chapter talks about the soa industry and how vendors are responsible for soa but are also causing problems at the same time. How standards organizations are working for soa but also competing at the same time. Pretty interesting stuff and even though this was the least technical chapter, not once was I bored. It ends by comparing Ssoa with older architectures. I especially like how the author differentiates between soa and "traditional" distributed architecture that uses web services. (hint: rpc has a lot to do with it)
Chapter 5 - Web services and primitive soa
I read the author's first soa book last year and this chapter seemed to repeat a few sections from that. But if I remember correctly it goes into more detail and provides case study examples that the first book didn't have. If you're a web services veteran you can probably skip this one.
Chapter 6 -Web Services and Contemporary SOA (Part I: Activity Management and Composition)
Here he goes up a gear and dives right into that scary thing we've been calling ws-* Everything from transactions to context mgmt to orchestration and so on is covered. I really felt the author did a brilliant job building this chapter up by starting with simple meps and building up to activity management and bpel and so on. He really showed how each adds a layer over the other and how all add layers to soa.
Chapter 7 - Web Services and Contemporary SOA (Part II: Advanced Messaging, Metadata, and Security)
Yup, the rollercoast ride continues here as he gets into addressing, reliable messaging, security and other ws-* specs. All of these are specs I had already heard about and I think this type of coverage is appropriate forwhere soa is going. I forgot to mention that in this chapter and 6 he introduces 'in plain english' sections that are hilarious. They are humorous analogies that compare these complex technologies to analogies he writes about a car wash. Good, fresh writing in the usual dull and dry techno world.
Chapter 8 - Principles of Service-Orientation
Essentially a whole bunch of theory about designing services and then eight specific 'principles' (dos and don'ts) about how to design services the right way for soa. I had to go back and reread this chapter after I finished the book. I sort of glanced thru it at first but then found out that later chapters really use these principles. When I went through it again I actually thought this was pretty important stuff. This really is the next oo. You can get this chapter for free at the book web site too.
Chapter 9 - Service Layers
STudy this if you're a application architect or enterprise architect. It shows what you canh do with services built with service-orientation. The diagrams showing different types of layers combined together are pretty cool.
Chapter 10 - SOA Delivery Strategies
If you're a PM you'll love this chapter. It gets into the different phases in a soa project and how you can reorganize them using 'delivery strategies' depending on your budgets and priorities. I'd pay extra close attention to the pros and cons parts where, after documenting these strategies in abstract, the author points out their true colors.
Chapter 11 + 12 - Service-Oriented Analysis I + II
Don't know where to start when it comes to figuring out your services? Well, the author lays it all out here. He provides a process for systemtically breaking down your business logic and divying it up into services. Chapter 12 is like an instruction manual about service model. Being froma web services background this was all new to me.
Chapter 13 - 16 - Service-Oriented Design I, II, III, IV
Roll up your sleeves man, because here is where you get into the real muck of building web services for an soa. There are a bunch of processes that hash out the nitty gritty of wsdl, xsd, and bpel and show you how to build services for the types of layers set up in ch.9. Tons of code and case study samples and tips for design. This is probably the most valuable part of the book for developers and architects.
Chapter 17- Fundamental WS-* Extensions
I forgot tomention that in chapters 6 and 7 no code samples are given. He only covered ws-* specs conceptually. All of the corresponding code is placed in this chapter. A bit inconvenient if you're a developer who wants to see the code while learning about the spec, but not tragic. The neat thing is he ties the code samples into the case studies. This was my first experience with ws-* in real world tyhpe scenarios.
Chapte r18 - SOA Platforms
The author documents j2ee and .net frameworks here first in total abstract and then about how they support the different parts of soa. This was very interesting because it related a lot of the concepts stuff to actual technology and the let you compare different technologies in how they support soa.
I recommend this book to colleagures and clients and I'm recommending it here. If you have questions about SOA then this book probably has the answers you're looking for. I say that because by the time I finished reading it I ran out of questions myself.
Service-Oriented Architecture (SOA): Concepts, Technology, and Design OverviewThis is a comprehensive tutorial that teaches fundamental and advanced SOAdesign principles, supplemented with detailed case studies and technologiesused to implement SOAs in the real world.***We'll have cover endorsements from Tom Glover, who leads IBM's WebServices Standards initiatives; Dave Keogh, Program Manager for Visual StudioEnterprise Tools at Microsoft, and Sameer Tyagi, Senior Staff Engineer, SunMicrosystems. All major software manufacturers and vendors are promotingsupport for SOA. As a result, every major development platform now officiallysupports the creation of service-oriented solutions.Parts I, II, and III cover basic and advanced SOA concepts and theory thatprepare you for Parts IV and V, which provide a series of step-by-step "howto" instructions for building an SOA. Part V further contains coverage of WS-*technologies and SOA platform support provided by J2EE and .NET.

Want to learn more information about Service-Oriented Architecture (SOA): Concepts, Technology, and Design?

>> Click Here to See All Customer Reviews & Ratings Now

Read More...