>the effort" out of the business logic per se, neither does it become
>"relatively simple". XML gateways do "in transit" kinds of things,
>i.e. they can translate, route, wrap, and unwrap. That can be
>difficult in itself. There is still a need for security, identity,
>roles, etc. in the business logic per se that requires a good bit of
>effort.
Implementation of a solid SOA Security Infrastructure is dependent on many
things that Enterprises have put into place before SOA came along, such as
Identity Management and PKI Infrastructure.
The attraction that a XML Security Gateway holds for me is two fold:
1) It is a "Gateway" to my services; As such it is a single point of policy
enforcement (Of course, it is incumbent on me as I build out my
infrastructure, to make sure that it is not a single point of failure by
load balancing/clustering them)
2) While I could do certain things such as digital signature checking, xml
schema validation etc. using my Java/.NET service platform, off-loading
those types of tasks to a hardware device such as an XML Security Gateway
provides me with a significant increase in performance.
Regards,
- Anil
SPONSORED LINKS
| Computer software | Computer aided design software | Computer job |
| Soa | Service-oriented architecture |
YAHOO! GROUPS LINKS
- Visit your group "service-orientated-architecture" on the web.
- To unsubscribe from this group, send an email to:
[EMAIL PROTECTED]
- Your use of Yahoo! Groups is subject to the Yahoo! Terms of Service.
