Udi Dahan is The Software Simplist, an expert on software architecture and design. A Solutions Architecture and Connected Systems MVP 4 years in a row, Mr. Dahan is also one of 33 experts in Europe recognized by the International .NET Association, an author and trainer for the International Association of Software Architects, and an SOA/Web Services/XML Guru recommended by Dr. Dobbs Journal (DDJ).
You are allowed to fail, as long as you fail differently every single time…
It’s with this idea in mind, and while failing differently several times, that Udi learned a ton of things on the projects he worked on.
Udi gave a talk about how to avoid the pitfalls of wrongly applying SOA in your applications design and development. Here, he shares them with us.
While not being completely sure about what can make your SOA project succeed, Udi shares things that will most likely make your SOA project fail.
Loose Coupling is at the heart of SOA. We should have tight coupling inside the services and loose coupling between them.
It’s not enough to have loosely coupled design-time artifacts. But you need to also have loosely coupled run-time artifacts. Otherwise you have a system that all crashes at the same time.
NServiceBus is a lighweight communication framework. You can get its binaries on nservicebus.com or by using Nuget.
It’s a key component when building SOA applications on the .NET platform.
Its default persistence system is RavenDB. NService bus uses the MS Distributed Transaction Coordinator. It also has a dependency for Log4Net logging service. Using NServiceBus in a project make you use NServiceBus.dll and NServiceBus.Core.dll.
Click the picture below to listen to one of Udi’s presentation about SOA.