Home
Business Guide
 
simplicable technology guide   »  enterprise architecture   »  service oriented architecture   »  the 9 principles of soa design

The 9 Principles Of Soa Design

        posted by , June 30, 2016

Service-oriented Architecture (SOA) is as simple as can be. There are 9 design principles to keep in mind when designing a SOA service:

1. Standardized Service Contract
Services adhere to a service-description.

service-contract

2. Loose Coupling
Services minimize dependencies on each other.

service-loose-coupling

3. Service Abstraction
Services hide the logic they encapsulate from the outside world.

service-abstraction

4. Service Reusability
Logic is divided into services with the intent of maximizing reuse.

service-reusability

5. Service Autonomy
Services should have control over the logic they encapsulate.

service-autonomy


6. Service Statelessness
Ideally, services should be stateless.
service-statelessness


7. Service Discoverability
Services can be discovered (usually in a service registry).

service-discoverability


8. Service Composability
Services break big problems into little problems.

service-composability


9. Service Interoperability
Services should use standards that allow diverse subscribers to use the service. This is considered so obvious these days that it is often dropped as a principle.

service-interoperability


These 9 principles are summarized in this handy reference chart:

soa-design-principles



Related Articles



Enterprise Architecture
How to architect an organization.




The following template captures your high level enterprise architecture.

How to architect an organization.

IT career management

Ever wonder when that hot new technology is going to get cheaper? Learn what really drives technology prices.


Recently on Simplicable


5 Common Current State Architectural Blueprint Mistakes

posted by Anna Mar
A current state architectural blueprint is essential to your success as an IT organization. After all, you can't effectively manage a complex architecture that's not documented.

9 Reasons You Need a Current State Architectural Blueprint

posted by Anna Mar
A current state enterprise architecture blueprint represents your organization's high level architecture. It's probably the most important documentation that any IT organization can create and maintain.

10 Big Data Definitions: Take Your Pick

posted by John Spacey
As with any emerging field, the definition of big data is always in flex.

9 ITIL Implementation Challenges

posted by Anna Mar
ITIL implementation is no cakewalk. ITIL impacts your entire organization — your business, your IT department and your inflight projects.

about     contact     sitemap     privacy     terms of service     copyright