blog.paulevans.name
Evans Expressions: September 2010
http://blog.paulevans.name/2010_09_01_archive.html
Here you will find my thoughts, wisdom and ramblings - enjoy! Thursday, September 30, 2010. Patterns of Web Service Versioning. One of the sessions I attended at JavaOne 2010 was titled: "Versioning Strategies for Service-Oriented Architectures.". Would be something "concrete" - such as adding a new piece of data to a message required by an operation. A semantic change. Might be something like the SLA requirements on the service changing - e.g., the SLA of a service changed from a 95% uptime requ...And I...
blog.paulevans.name
Evans Expressions: May 2010
http://blog.paulevans.name/2010_05_01_archive.html
Here you will find my thoughts, wisdom and ramblings - enjoy! Sunday, May 16, 2010. Create Clear, non-Leaky Component Interfaces. One of the tenants of object-oriented design is encapsulation. The basic premise of encapsulation is that an object has a contract exposing its publicly available functionality while the implementation of the contract should be completely hidden. Such a design allows implementations to change and evolve without the consumer of the object being aware. Why is this good? Here's a...
blog.paulevans.name
Evans Expressions: August 2010
http://blog.paulevans.name/2010_08_01_archive.html
Here you will find my thoughts, wisdom and ramblings - enjoy! Tuesday, August 3, 2010. My Take on the Document/Literal 'Wrapped' Idiom. If you've designed and built web services you've more than likely come across the "wrapped" idiom. I like the wrapped idiom - we're talking of course with the assumption that the binding used is the SOAP binding (one of 2 out-of-the-box. So - why am I writing about this? Or an action,. Whatever you want to call - just DON'T call it the operation or the method or the func...
blog.paulevans.name
Evans Expressions: June 2010
http://blog.paulevans.name/2010_06_01_archive.html
Here you will find my thoughts, wisdom and ramblings - enjoy! Friday, June 18, 2010. Random Thoughts on Loose Coupling. Some random thoughts on loose coupling:. Loose coupling is not just an idea, it's a way of thinking; a mode of thought when designing software. Within the context of software development, coupling can be said to be a measure of the number of assumptions 2 systems make of each other within the context of integration. Why is loose coupling good? Put it once, "software is complex because t...
SOCIAL ENGAGEMENT