• Post Reply Bookmark Topic Watch Topic
  • New Topic
programming forums Java Mobile Certification Databases Caching Books Engineering Micro Controllers OS Languages Paradigms IDEs Build Tools Frameworks Application Servers Open Source This Site Careers Other Pie Elite all forums
this forum made possible by our volunteer staff, including ...
Marshals:
  • Campbell Ritchie
  • Jeanne Boyarsky
  • Ron McLeod
  • Paul Clapham
  • Liutauras Vilda
Sheriffs:
  • paul wheaton
  • Rob Spoor
  • Devaka Cooray
Saloon Keepers:
  • Stephan van Hulst
  • Tim Holloway
  • Carey Brown
  • Frits Walraven
  • Tim Moores
Bartenders:
  • Mikalai Zaikin

Book: High-assurance design for Web services ?

 
Greenhorn
Posts: 12
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
Hi Cliff,

Does your book discuss a high-assurance design for XML Web services ? What are the complexities ? If so, how it can be accomplished ? It would be nice, if you could highlight a H-A design scenario for Web services ? Do you have a case-study how to make it work ?

Thanks

Vijay P.
[ January 19, 2006: Message edited by: Ilja Preuss ]
 
Author
Posts: 22
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
Hi Vijay,

In general, the book does not contain technology-specific material. The original draft did, but it would have ended up being 1000 pages, and I decided it would take too much to get it all to print in a reasonable time and keep it current. Technology-specific material becomes dated so quickly. The slimmed down (660-page) book discusses principles that apply to any technology, be they web services, EJB, HTTP, or whatever.

But that does not provide an answer to your real question.

Two of the case studies in my book are for a system that contained a significant web service component (using WebMethods). The book does not highlight that. This is a huge topic, and deserves a book in its own right. (Perhaps someone will write one! - let them keep it up to date! LOL) Some of the sources of unreliability of web services are poorly thought out transaction states (what happens if a service request fails?), thoughtlessly combining web services (this is discussed in my book), and scalability (which is not discussed in my book). Sources of vulnerability include misconfiguration of security proxies, denial of service, a failure to use SSL, and schema attacks. Web services can benefit greatly from application-level security appliances, and there are many such products (NetContinuum, Secure Computing, Finjan). Sorry to dump all this on you - there is no simple answer. - Cliff
reply
    Bookmark Topic Watch Topic
  • New Topic