Skip to end of metadata
Go to start of metadata

Quick answer: If you are going the SOA route as an important system strategy, you need to start thinking about what a service is, how they relate to each other and how they differ and make great building blocks for use/reuse - hence Service categorization. If you are writing a (silo) application, which only consumes a few WebServices, you are home free, not bothering with service categorization.

Key takeaways:

  • You easily learn that you do have different types of services
  • Each category of services have their own requirements to technical infrastructure
  • Each category of services have their own design rules (governance)
  • To build a SOA, you need to have a precise definition of what a service is which is meaningful.

Relationship to other SOA strategies

Add entry

The Laws of SOA

Add entry

Service Manifest

Add entry

Design-Time Governance - SOA Design Rules

Add entry

  • [Question still to be asked..]

NB! Feel free to add any question you might have here

Enter labels to add to this page:
Please wait 
Looking for a label? Just start typing.