When designing components for a SOA landscape (or any multiprocess system), the primary concern is with the communication behavior of the component: how messages are passed to and from the component and in what order, what those messages are and
Letting go: yet another traditional problem in the SOA world
Over the past few days my thoughts have been drawn to what I think is a common problem (in addition to the ones identified by Freddie van Rijswijk in his recent blog) in establishing and participating in a SOA architecture:
Will SOA and BPM bring the MOOSE Savings and Business Agility?
How is SOA and BPM going to improving the ability to serve and exceed quality while cut in the 30% cost of IT MOOSE? I´m convinced that SOA and BPM is NOT the answer. The discussion on ROI of SOA
SOA and the domain: how new technology should not blind you to old wisdom
A couple of things happened to me over the past few days as I was taking on a new role within a new project that caused me to ponder a bit about the role of domains and domain driven development
Service orientation within applications
Many IT projects at large companies aim to make the company “SOA-proof”. What really concerns me is that time after time software architects tend to treat “XML Web Services” as a synonym for “Service”. In this article, I want to
Why are web services so different from an HTML user interface?
We all know how a typical web application is usually built up. The image at the side rougly displays the different layers that are to be found in an application. Typically, the user interface layer receives HTTP requests, calls one
Should we send out a SOS for SOA?
This Post is all about laughing and not to worry to much about SOA, BPM, ROI, CEP. I came across “Greg the Architect” and his small movies underpin a lot of what i have written about lately. If you do