Yet a nother installment in the SOA Pattern of the week series. This time the topic is Service Decomposition: Why and how to split up services after their initial deployment.
I wrote down another SOA Design Pattern that was published as a candidate pattern at soapatterns.org. This pattern is a way to avoid problems that may arise when one message is processed multiple times.
I wrote down a description of a SOA Design pattern that was published at soapatterns.org as a candidate pattern. It is about accepting crappy input data and still perform the service that your consumers wants done. Useful when you have legacy consumers for your service.
I like them
Jun 18, 6:47am
Meet another member
