In this post I am raising the question about how to deal with race conditions in asynchronous service invocations. I have seen possible solutions in BizTalk and WF scenarios but they are both pretty messy and have their own race condition issues. What do you do to address these issues in your solutions?
I have always considered testing to be an important part of quality software development, however I find the focus on unit testing in commercial environments is worrying, particularly when combined with junior developers. What has this to do with science and mathematics? Read on…
Recently, I have been working on an SOA project using WCF. As development moved toward integration of multiple services I found the coupling of services to be a real pain point. Although services operated in a loosely coupled fashion, the actual implementation of the services was less ideal.
Many low-end and middle-end web CMS providers profess (indeed stress) scalability and extensibility but in my experience the architectures of those systems are fundamentally flawed in achieving these aims. What are your thoughts?
