Abstract
Growing number of reports on the problems with SOA projects indicates that SOA faces substantial problems. It can be a consequence of the fact that SOA passes the disgustion phase of the hypo curve.
It, however, must have some concrete reasons. We analyze frequently used and often even recommended SOA development practices and processes and we show that the processes implicitly apply few known and usually most important SOA antipatterns.
The cure is not easy. We show using causal diagrams to analyze dependencies that the practices involve developing (unstable) causal cycles.
It requires strong managerial countermeasures a a careful analysis. We show that the most important is to avoid fine-grained services and interfaces.