How to Document Cloud Design Decisions
When developing and integrating cloud systems, the public interfaces and
external "contracts" among services mean that design and architecture can
evolve rapidly and in parallel. But when they do and the teams are not in
the same room, this speed is an invitation to chaos. As two teams work on
opposite sides of an interface (the service provider and the service
consumer), it's easy for the teams' definition of variables and methods to
fall out of sync. Of course the service provider team could update its
document and notify the other team about a new semantic of a field value or
behavior of a service. But the reality is too often that they don't, and
the classic problem of distributed version control rears its ugly head.

http://bit.ly/yO27JY

Source:
http://www.networkworld.com/news/2012/012612-how-to-document-cloud-design-255376.html
See if people are clicking on this link: http://bit.ly/yO27JY+
Try the bitly.com sidebar to see who is talking about a page on the web:
http://bitly.com/pages/sidebar

List archives at http://lists.ufl.edu/archives/recmgmt-l.html
Contact [log in to unmask] for assistance
To unsubscribe from this list, click the below link. If not already present, place UNSUBSCRIBE RECMGMT-L or UNSUB RECMGMT-L in the body of the message.
mailto:[log in to unmask]