The Early Adopter Weblog covers Don’s tenets of Indigo:
There are some major tenets of Indigo, and getting into this mind set is fairly critical:
Boundries are explicit – Your web services defined boundaries which must be respected. Your Web service is dealt with at the boundary, but anything within the boundary is none of the callers business.
Services are autonomous – A service should be able to get done what it’s asked to do, with minimal dependence on others.
Share schema, but not class – Schemas are structural. Contracts are behavioral. This is what you’re sharing. Forget about sharing classes.
Policy based compatibility – Say what your service provides. If someone needs something, and you provide it, great. Otherwise, you’re not compatible, and that’s ok. It’s OK because they can look at your policy and know in advance that you don’t support certain things.
No comments yet.
Sorry, the comment form is closed at this time.
