SOA and Web Services
Service-oriented architecture (SOA) is an architectural approach to development that turns traditional techniques upside down. SOA encourages organizations to think in terms of actual business services and the associated data, rather than low level technology details. Instead of developing applications from the ground up, SOA frees organizations to start with high level business definitions for data, interfaces, documents, and processes. SOA then maps these high level service definitions onto new or existing infrastructure, regardless of the details, location, or programming language in which the systems were written.

Some questions that I can answer include:
What is SOA and where do Web Services fit in?
How do I identify the "right" services?
How do I ensure that the re-architect system continues to meet or exceed the current SLAs (performance, concurrency, availability, etc.)?
Do I need an ESB? If so, which one and where does it fit in the overall picture?
How can I leverage the principles of decoupling using Event Driven Architecture (EDA) in my SOA?

<<Back to Skills and Benefits Continuum™