Implementation of web services has been slow because some people see it as a technology problem. We see people get frustrated when they try to implement their web services with only tools. That approach solves only part of the problem; it is like thinking you can build an accounting system with just a COBOL compiler. The compiler is required, to be sure, but it is only invoked after needs are analyzed, a system is architected, and the green light is given for implementation.
Mae Ozkan
Architects and developers must view their operation in a different way. Instead of focusing only on tools, implementers also need to think about their entire operation from services point-of-view and automate the processes they want to share. Only after those processes are automated and working will implementers be able to expose them as services to internal or external systems. There are great tools creating web services applications, but those applications will be much more robust if architects and developers understand the larger structural issues.
Product Details
Would you like to update product info or give feedback on images?
|
|
Share your thoughts with other customers:
|
||||||||||||||||||||||
|
Most Helpful Customer Reviews
2 of 2 people found the following review helpful:
4.0 out of 5 stars
Get started with web services,
By xmlguru001 (Seattle, WA) - See all my reviews
This review is from: Web Services Implementation Guide, Volume 1: Getting Started (Paperback)
This book is one of many new titles on web services (the book's introduction makes the case for using a lowecase-w in "web" services). Most of the books that I have seen cover the world of web services in terms of this or that tool. Java J2EE, Microsoft .NET, IBM Web Services Toolkit, etc.This book gets beyond a particular implementation of code and talks about the business reasons for implementing web services. This includes planning, automating processes behind the firewall, determining security issues and so forth. This is the only book I have seen that covers such architectural facets. As a developer, I found the coverage of the technologies very helpful. As my company's chief architect, I found many things to think about in the book. The book covers the standards (XML, XSD, SOAP, WSDL) in a very accessible way, with witty commentary so it does not get boring. This is quite a feat for such an acronym-rich technology.
1 of 1 people found the following review helpful:
5.0 out of 5 stars
Excellent Web services resource for Architects & Managers,
By Darshan Singh (Algonquin, IL United States) - See all my reviews
This review is from: Web Services Implementation Guide, Volume 1: Getting Started (Paperback)
Real life examples, diagrams, easy to read, and is up-to-date - this book is recommended for architects, managers, developers, who would like to get a good understanding of SOAP and XML Web services. This book contains answers to your "what", "why", and "how" questions pertaining to XML Web services. The chapters flow nicely. It also talks about BizTalk and ebXML and how they fit in Web services paradigm. This first volume ends with discussion on more recent Web services standards (WS-****).
1 of 1 people found the following review helpful:
5.0 out of 5 stars
Learned so much!,
By Jessica (XML Guru) - See all my reviews
This review is from: Web Services Implementation Guide, Volume 1: Getting Started (Paperback)
I read the book very easily. It thought me so much about web services, how it evolves and where it is going to. It cleared many questions I had in my mind. I am technically enhanced now! It is fantastic to understand the cool technologies.
Share your thoughts with other customers: Create your own review
|
|
Tags Customers Associate with This Product(What's this?)Click on a tag to find related items, discussions, and people.
|