Web Services Strategies
Beyond the technology, IT strategies for implementation of Web services by Doug Kaye.
|
Most Enterprises Also Failed With Components. On CBDI Forum, author David Sprott (I believe) wrote. "Enterprises are discovering many of the core issues that inhibited use of software components apply equally to Web Services. Is this a reason for avoiding Web Services, or are there ways to over come them?" His answers are (to summarize):
- Make a real business case.
- Find the silver bullet.
- Use an external platform -- Pay as you go.
- Find services that are not business critical.
Doesn't make sense to me. If you're going to implement web services that aren't business critical, then they're probably rather simple and may not even need a real business case. More likely, you'll be using web services in these situations as just the "right way" to accomplish an integration task. It's when you implement services that are truly business critical that you need both a robust deployment platform as well as a justifiable business case. I refer to these as "complex" web services, and they're those that also require some degree of strategic planning.
Posted Saturday, May 10, 2003 5:21:51 PM 
|
|
|
A Framework for SOA. CDBI offers this framework for planning SOA implementation, with candidate deliverables for architects, and invite feedback. They've coined the phrase "Business Services Bus" to tie together services into logical sets that reflect the structurea of businesses. Good ideas, but instead of "the logical grouping and design of each bus ensures that there is minimal duplication plus uniformity in naming, ordering, and types of parameters" I'd like to see them focus on more loosely coupled concepts. Specifically, the functions of a department should be express in a set of coarse-grained documents and XML schema.
Posted Saturday, May 10, 2003 4:55:38 PM
|
|
|
|
|
|
