Prev
Page | Table of Contents | Next
Page
Web
Services - Low Hanging Fruit
|
| - Advertising - |
 |
The Reactivity XML Firewall delivers instant and sustainable
XML Web services security in an appliance securing all XML Web
services traffic. The Reactivity XML Firewall allows enterprises
to protect against XML Threats while maximizing application
productivity. The Reactivity XML Firewall is the market's most
powerful and configurable security policy manager, with turnkey
infrastructure integration and optimized traffic throughput.
Learn more
about Web Services Security... |
| |
|
|
The prevailing wisdom is that the ultimate adoption of Web Services
in the enterprise will largely focus on helping to solve the B2B
problem, where a need exists for low overhead solutions and 'ubiquitous'
environments in which businesses can find each other (the Web, http)
and perform some basic interactions over the Internet. The problems
experienced to date in achieving B2B collaboration between partners
were largely due to a lack of trust (and good security technology)
by companies in exposing their databases and applications to each
other. Centralizing the relevant information that companies choose
to share, without exposing the entire application, is the goal for
many software companies who will leverage the web in their B2B applications.
But, as we've seen, you have to get your own internal house in
order to best capitalize on the efficiencies of B2B. Therefore most
activity now (vendor positioning and product roadmaps) centers on
how Web Services can be used to facilitate faster enterprise application
integration. Usage in this domain offers the most short-term benefits
if it can contribute to easing the pain of integration. It's a natural
extension of middleware type architecture problems the industry
has been trying to solve: how to best share data between applications
and underlying architectures and reuse components. In fact, those
of us that remember the advent of CORBA (common object request broker)
and object-oriented programming began by scratching our heads as
we attempted to figure out how different the Web Services paradigm
is from these other standards.
Here's the answer: The introduction of object-based technologies
in the early to mid 90's promised component reuse for application
development. But the fact is, this technology is complex, hard to
use, and requires technically savvy developers and architects. Web
Services are an extension of this component-based model but the
difference is that Web Services are loosely coupled (not tightly
integrated) and they are built on existing ubiquitous protocols
like HTTP and XML. The goal for Web Services is to enable businesses
to access parts of an application and integrate it with data from
other applications, business process platforms, or infrastructure
functionality and bind them together to deliver a composite application
or applet that can be accessed from anywhere using the Internet.
Prev Page | Table
of Contents | Next Page
Barbara Angius Saxby (barbara@accelentmarketing.com)
founded Accelent (www.accelentmarketing.com)
to help software startups accelerate marketing strategies, planning,
and execution. She specializes in positioning and launching enterprise
infrastructure and application companies. Barbara is a senior marketing
executive with over 20 years experience in strategic marketing management
and has done extensive work internationally.
| 
