Services share schema and contract, not class – Utilization of standards based mechanisms for defining a services structure and behavior will allow Global Bank to expose functionality as services on many of its existing legacy systems whilst developing new services and clients on the .Net platform upon which it has chosen to develop Global Bank.

Guidelines include:
- Services utilize schema to define data and contracts for behavior.
- Message validity should be verified using machine validatable schema.
- Contracts and schema should be stable over a period of time ensuring that consuming applications do not need to be updated as would be the case if a schema was updated on a service


Please insert random remarks / discussion here:





See Also: GlobalBankWiki