Udi Dahan   Udi Dahan – The Software Simplist
Enterprise Development Expert & SOA Specialist
    Blog Consulting Training Articles Speaking About

One wrong DLL = 3 months gone

Saturday, June 24th, 2006.

A couple of days ago, one of the programmers on a project I’m consulting on came in to ask me a question. With a puzzled look on his face, Alex asked me “Udi, in your design you have these two tiny interfaces, IEntity and IMapEntity, that together wouldn’t justify belonging in their own DLL, and you gave each of them their very own DLL! Why?!” Right then and there I decided to hold a project-wide standup. I got everyone into the room, from project manager, to tester, to programmer, and spun the following scenario.

“Patrick”, I said to the project manager, “you know how we have our iterations set up so that each iteration we work on an entire feature, end to end, and keep the number of features down?” Patrick nodded.

“And Daniel”, I said to our test lead, “you know how you report defects on a feature by feature basis, correlated with the version of the system being tested?” Daniel, too, nodded.

“And Beth”, I said to our SCM/integrator, “you know how each check-in gets the relevant project’s version number to increase, gets built, unit tests run, and, if everything’s OK, the DLL gets put out?” Beth was quick to jump in, “and don’t forget that the version number is taken from the DLL and applied as a label to the corresponding source files.”

“So, what’s the point of all this ceremony?” I asked, turning to the entire group. I got some blank stares. “Why are we doing things like this, and not differently?” Alex spoke up. “This all has to do with the DLL thing I asked you before, doesn’t it?”

I won’t draw this story out too much, so let’s just cut to the chase.

When a tester logs a defect, that defect is tied to a feature and a system wide version number. From that version number, we can find all the specific version numbers of the DLLs that comprise that system wide version number. We can also see which DLLs have changed from the previous iteration. From there, we can find the tree of DLLs which are somehow dependent on those few that have changed. Only a few change because we keep our iterations small. From the specific version of a DLL, we can go into our source control repository and, from the label, find the exact source which comprised that DLL. Those are the source files that a programmer has to sift through in order to locate the origin of the defect.

Obviously, if there is less source to go through, the programmer will, on average, find the origin of the defect faster. And, as we all know, it usually takes longer to find the bug than to actually fix it.

So, by splitting up different classes and interfaces into different DLLs, we can manage dependencies in the system so that less source needs to be examined. For instance, in the case of the interfaces mentioned above, IMapEntity depends on IEntity. However, there are multiple classes that depend on IEntity (like views and presenters/controllers) which don’t really care above IMapEntity. The opposite isn’t true, though. The renderer and layer classes are dependent both on IEntity and IMapEntity. If these two interfaces were in the same DLL, and for a new feature we needed to add the “AlphaBlend” property to IMapEntity, when a bug would be found in that iteration, all the view and presenter classes would have to be examined as well. This is because the version number of the IEntity/IMapEntity DLL would have increased, and all the dependent DLLs could have been adversely affected by that change. Had these two interfaces been separated into different DLLs, this alpha blend change would have left an entire tree of DLLs uninvolved. This means less source for a programmer to look through, which means less time to get the feature working.

While I’m not sure the statement “1 wrong DLL = 3 months gone” is necessarily true, I can’t say it isn’t either. All these tiny little things add up to either huge productivity gains, or losses. Especially when you consider larger, more complex projects. A good design, by itself, can’t save you from the failure conditions described above. You need all the practices in place, working in harmony, and people paying attention to make the project succeed.

That’s if the politics don’t nail you first 🙂

If you liked this article, you might also like articles in these categories:

Check out my Best Content If you've got a minute, you might enjoy taking a look at some of my best articles.
I've gone through the hundreds of articles I've written over the past 6 years and put together a list of the best ones as ranked by my 5000+ readers.
You won't be disappointed.

Subscribe to my feedIf you'd like to get new articles sent to you when they're published, it's easy and free.
Subscribe right here.

Follow me on Twitter Follow me on Twitter @UdiDahan.

Something on your mind? Got a question? I'd be thrilled to hear it.
Leave a comment below or email me, whatever works for you.

  1. Chris Sterling Says:

    I entirely agree and use many of the same practices when developing a product for our customers. Our entire Professional Services division runs their projects using Scrum and many of the Agile development best practices such as TDD, continuous integration, collective code ownership, most use pair programming, and others.

    What we have found to be one of the biggest time savers, and therefore money savers for our customers, is the use of an agreed upon versioning system for our projects. This is a cross-cutting concern which involves our SCM, project dashboards, project structures, requirements tracking, and issue tracker. It comes down to having the right infrastructure in place to make getting work done much easier.

    Now, most of the projects I work with are Java based but they have similar issues as described above. We use Maven 2 to build, test, deploy, and view project dashboard across these projects. We found this to be so helpful that we even created plugins (or Mojos as they put it) for our .NET projects. Reports for FxCop, NDepend, NUnit, and others all get placed into the Maven 2 dashboard. It can even build our solutions.

    The consistency allows our developers to help across project lines without dealing with as much getting up to speed homework. It doesn’t eliminate it, but we are working on that. 😉

  2. John Wood Says:

    While there may be benefits specific to your project, in my experience more DLLs simply equates to more headaches.

    >> From that version number, we can find all the specific version numbers of the DLLs that comprise that system wide version number. <<

    But why. From a version number you can go to source control and see what changed between labels. What does this have to do with DLLs? The only source they have to look through will be a diff report between those two version labels.

    I think there are very few reasons to separate /components/ into their own DLLs, let alone individual interfaces. In my mind DLLs are a necessary evil – necessary only when sharing classes or interfaces between modules.

    Surely you’ve heard the phrase ‘DLL hell?’ – it’s not limited to COM at all. It’s limited to anything that is deployed piecemeal. The more granular your deployment, the more room there is for errors caused by mismatched DLLs, or a botched compilation that linked against the wrong DLLs. In my experience it causes FAR more headaches than it’s worth. I’m 100% a proponent of deploying applications as an atomic entity. Even patches go out as the entire thing, just to ensure that somebody doesn’t apply a patch in the wrong order and mess everything up. You say it reduces the source code – but I don’t see it. A DLL means an extra project file, extra references list, extra using statements, the list goes on. And this isn’t to mention the performance hits of all those assembly resolutions. In my experience you can increase the size of the project by an order of magnitude by being DLL happy.

  3. Paul Louth Says:

    Your methods of defect hunting are crazy. Do you really check all code/DLLs that have changed? I think most experienced developers would instinctively know where to look and would then do a diff on the source file(s) in question. Checking DLL version numbers to see what’s changed seems insane to me, and increasing the DLL count just means more headaches.

    Also if you were on my project and randomly downed-tools to grandstand in front of the whole team then I’d fire you. There’s no room for prima donna programmers of development teams in my opinion.

    And your grandstanding adds-up too does it not?

    One Prima Donna Coder = 3 Months Gone

  4. Mehran Nikoo Says:

    Components (assemblies in .NET terms) are units of deployment. This should ideally be the main deciding factor for the number of components in the application. For example if you want to be able to install only part of the application (i.e. the core framework) without optional components, you need to break it down to multiple components.

    Same applies if you want to minimise the number of files that need to be re-deployed in a patch release. But be careful. If your application has too many components, it is very likely that a bug fix needs many components to be re-deployed. Look at Windows service packs for instance; they include hundreds of updated files, which is defeating the purpose of minimising the number of re-deployed files and could end up in versioning conflicts too.

    In terms of development, in the same way that having one large project (and therefore one assembly) can prove to be very slow, having too many projects with project references will have the same effect as the referenced projects need to be recompiled and the references in parent projects need to be updated, and this process can be repeated many times, based on the depth of project reference tree.

    As you mentioned, it is up to the solution architect to decide which way to do based on project environment and complexity.

  5. Udi Dahan - The Software Simplist Says:

    First of all, thanks for all the comments. Take my suggestions in the context of large, complex projects with numerous developers and teams, and even companies working on the same project. The kinds of project where the average success rate doesn’t even make double digits.


    1. Not all source is necessarily in a single repository.
    2. By having more granular deployment, and smaller iterations, a smaller percentage of your deployment footprint changes each time. That means higher stability.


    I shall consider myself fired. But, for those clients who haven’t fired me yet…

    I’m not worried about the cases where programmers quickly home in on a bug, fix it, and move on. I’m worried about the bugs that don’t show up on the programmers machine, or sometimes do, and sometimes don’t. I’m worried about bugs that we thought we fixed 2 iterations ago, but have suddenly come back. These are the kinds of things that eat up project time, and don’t behave deterministically.


    By following my “first principle of design”, I usually avoid the problems you describe. See:

  6. John Wood Says:

    >> Not all source is necessarily in a single repository. > By having more granular deployment, and smaller iterations, a smaller percentage of your deployment footprint changes each time. That means higher stability. <<

    I disagree. That means lower stability because you cannot be sure what it is they’re running without looking at the version number of each and every DLL. The more unknowns there are, the less stable the system is. When you release everything from source control it is controlled – if you have a good build system it can dump out what has changed since the last build was performed (including the files) so you can be absolutely sure what it is they’re getting. I mean, if you don’t know what your build produces then what hope is there?

    Like I said, it greatly depends on your setup and the nature of your development – but I can say that for at least 5 larger projects I’ve worked on, they were each in DLL hell until we made the decision to move towards holistic deployment.

  7. John Wood Says:

    A bit that somehow got missed…

    >> Not all source is necessarily in a single repository. <<

    Well that’s probably your biggest problem. I would make a point of converging the source depots even if it means having a process that pulls stuff from other SCCSs nightly.

  8. Udi Dahan - The Software Simplist Says:

    Would you take responsibility for the build process for another company’s deliverables? I wouldn’t. Each company has their own process, and you just can’t change that. The integration I perform needs to be done at the level of modules (or CSCIs as they’re called in my industry), where each CSCI can be made up of numerous assemblies, config files, databases, etc.

  9. John Wood Says:

    But Udi, from what you were saying it sounded like this was *your* decision – after all, you were the one who took the team into a room to justify yourself. From what you were describing it sounded like you already had taken responsibility for the build process, given this has a direct effect on the granularity of deployment. You say “the integration I perform” – yet what you were describing was a decision on whether to create DLLs for each and every interface. That’s not integration, that’s development and that’s taking a direct role in deciding how the developed components are deployed. Or did I miss something?
    It’s not worth me harping on because without being directly involved in the project it’s impossible for me to construct any informed opinions. But from what I’ve understood from the little I have read, I just don’t see the justification.

  10. Udi Dahan - The Software Simplist Says:


    As the architect for the whole system, I am responsible for making sure that when we connect all the pieces together, and they don’t work, we’ll be able to quickly find out why.

    The fact that some of these pieces are developed at other companies doesn’t change that. Also, beyond affecting what interfaces those pieces expose/implement, I can’t dictate how those companies develop/build their pieces. I want to receive from those companies binary artifacts whose behavior I can verify (with unit tests, for instance).

    Although I wish that I could positively affect those other companies’ build processes, its more important for me to focus on the team, or teams, in my company.

    As to the issue of whether an interface being an element of development or integration – I think that its both, if done right.

    Consider the case where 2 or more companies depend on a common package, like the one containing IEntity. Its really important for me to know that all the binaries provided by all companies were developed and tested against the same version of that shared package, otherwise there’s a good chance that things will break in unexpected ways (depending on the backwards and forwards compatibility characteristics of that package).

    Of course, such a process may not scale down so well.


Don't miss my best content


Bryan Wheeler, Director Platform Development at msnbc.com
Udi Dahan is the real deal.

We brought him on site to give our development staff the 5-day “Advanced Distributed System Design” training. The course profoundly changed our understanding and approach to SOA and distributed systems.

Consider some of the evidence: 1. Months later, developers still make allusions to concepts learned in the course nearly every day 2. One of our developers went home and made her husband (a developer at another company) sign up for the course at a subsequent date/venue 3. Based on what we learned, we’ve made constant improvements to our architecture that have helped us to adapt to our ever changing business domain at scale and speed If you have the opportunity to receive the training, you will make a substantial paradigm shift.

If I were to do the whole thing over again, I’d start the week by playing the clip from the Matrix where Morpheus offers Neo the choice between the red and blue pills. Once you make the intellectual leap, you’ll never look at distributed systems the same way.

Beyond the training, we were able to spend some time with Udi discussing issues unique to our business domain. Because Udi is a rare combination of a big picture thinker and a low level doer, he can quickly hone in on various issues and quickly make good (if not startling) recommendations to help solve tough technical issues.” November 11, 2010

Sam Gentile Sam Gentile, Independent WCF & SOA Expert
“Udi, one of the great minds in this area.
A man I respect immensely.”

Ian Robinson Ian Robinson, Principal Consultant at ThoughtWorks
"Your blog and articles have been enormously useful in shaping, testing and refining my own approach to delivering on SOA initiatives over the last few years. Over and against a certain 3-layer-application-architecture-blown-out-to- distributed-proportions school of SOA, your writing, steers a far more valuable course."

Shy Cohen Shy Cohen, Senior Program Manager at Microsoft
“Udi is a world renowned software architect and speaker. I met Udi at a conference that we were both speaking at, and immediately recognized his keen insight and razor-sharp intellect. Our shared passion for SOA and the advancement of its practice launched a discussion that lasted into the small hours of the night.
It was evident through that discussion that Udi is one of the most knowledgeable people in the SOA space. It was also clear why – Udi does not settle for mediocrity, and seeks to fully understand (or define) the logic and principles behind things.
Humble yet uncompromising, Udi is a pleasure to interact with.”

Glenn Block Glenn Block, Senior Program Manager - WCF at Microsoft
“I have known Udi for many years having attended his workshops and having several personal interactions including working with him when we were building our Composite Application Guidance in patterns & practices. What impresses me about Udi is his deep insight into how to address business problems through sound architecture. Backed by many years of building mission critical real world distributed systems it is no wonder that Udi is the best at what he does. When customers have deep issues with their system design, I point them Udi's way.”

Karl Wannenmacher Karl Wannenmacher, Senior Lead Expert at Frequentis AG
“I have been following Udi’s blog and podcasts since 2007. I’m convinced that he is one of the most knowledgeable and experienced people in the field of SOA, EDA and large scale systems.
Udi helped Frequentis to design a major subsystem of a large mission critical system with a nationwide deployment based on NServiceBus. It was impressive to see how he took the initial architecture and turned it upside down leading to a very flexible and scalable yet simple system without knowing the details of the business domain. I highly recommend consulting with Udi when it comes to large scale mission critical systems in any domain.”

Simon Segal Simon Segal, Independent Consultant
“Udi is one of the outstanding software development minds in the world today, his vast insights into Service Oriented Architectures and Smart Clients in particular are indeed a rare commodity. Udi is also an exceptional teacher and can help lead teams to fall into the pit of success. I would recommend Udi to anyone considering some Architecural guidance and support in their next project.”

Ohad Israeli Ohad Israeli, Chief Architect at Hewlett-Packard, Indigo Division
“When you need a man to do the job Udi is your man! No matter if you are facing near deadline deadlock or at the early stages of your development, if you have a problem Udi is the one who will probably be able to solve it, with his large experience at the industry and his widely horizons of thinking , he is always full of just in place great architectural ideas.
I am honored to have Udi as a colleague and a friend (plus having his cell phone on my speed dial).”

Ward Bell Ward Bell, VP Product Development at IdeaBlade
“Everyone will tell you how smart and knowledgable Udi is ... and they are oh-so-right. Let me add that Udi is a smart LISTENER. He's always calibrating what he has to offer with your needs and your experience ... looking for the fit. He has strongly held views ... and the ability to temper them with the nuances of the situation.
I trust Udi to tell me what I need to hear, even if I don't want to hear it, ... in a way that I can hear it. That's a rare skill to go along with his command and intelligence.”

Eli Brin, Program Manager at RISCO Group
“We hired Udi as a SOA specialist for a large scale project. The development is outsourced to India. SOA is a buzzword used almost for anything today. We wanted to understand what SOA really is, and what is the meaning and practice to develop a SOA based system.
We identified Udi as the one that can put some sense and order in our minds. We started with a private customized SOA training for the entire team in Israel. After that I had several focused sessions regarding our architecture and design.
I will summarize it simply (as he is the software simplist): We are very happy to have Udi in our project. It has a great benefit. We feel good and assured with the knowledge and practice he brings. He doesn’t talk over our heads. We assimilated nServicebus as the ESB of the project. I highly recommend you to bring Udi into your project.”

Catherine Hole Catherine Hole, Senior Project Manager at the Norwegian Health Network
“My colleagues and I have spent five interesting days with Udi - diving into the many aspects of SOA. Udi has shown impressive abilities of understanding organizational challenges, and has brought the business perspective into our way of looking at services. He has an excellent understanding of the many layers from business at the top to the technical infrstructure at the bottom. He is a great listener, and manages to simplify challenges in a way that is understandable both for developers and CEOs, and all the specialists in between.”

Yoel Arnon Yoel Arnon, MSMQ Expert
“Udi has a unique, in depth understanding of service oriented architecture and how it should be used in the real world, combined with excellent presentation skills. I think Udi should be a premier choice for a consultant or architect of distributed systems.”

Vadim Mesonzhnik, Development Project Lead at Polycom
“When we were faced with a task of creating a high performance server for a video-tele conferencing domain we decided to opt for a stateless cluster with SQL server approach. In order to confirm our decision we invited Udi.

After carefully listening for 2 hours he said: "With your kind of high availability and performance requirements you don’t want to go with stateless architecture."

One simple sentence saved us from implementing a wrong product and finding that out after years of development. No matter whether our former decisions were confirmed or altered, it gave us great confidence to move forward relying on the experience, industry best-practices and time-proven techniques that Udi shared with us.
It was a distinct pleasure and a unique opportunity to learn from someone who is among the best at what he does.”

Jack Van Hoof Jack Van Hoof, Enterprise Integration Architect at Dutch Railways
“Udi is a respected visionary on SOA and EDA, whose opinion I most of the time (if not always) highly agree with. The nice thing about Udi is that he is able to explain architectural concepts in terms of practical code-level examples.”

Neil Robbins Neil Robbins, Applications Architect at Brit Insurance
“Having followed Udi's blog and other writings for a number of years I attended Udi's two day course on 'Loosely Coupled Messaging with NServiceBus' at SkillsMatter, London.

I would strongly recommend this course to anyone with an interest in how to develop IT systems which provide immediate and future fitness for purpose. An influential and innovative thought leader and practitioner in his field, Udi demonstrates and shares a phenomenally in depth knowledge that proves his position as one of the premier experts in his field globally.

The course has enhanced my knowledge and skills in ways that I am able to immediately apply to provide benefits to my employer. Additionally though I will be able to build upon what I learned in my 2 days with Udi and have no doubt that it will only enhance my future career.

I cannot recommend Udi, and his courses, highly enough.”

Nick Malik Nick Malik, Enterprise Architect at Microsoft Corporation
You are an excellent speaker and trainer, Udi, and I've had the fortunate experience of having attended one of your presentations. I believe that you are a knowledgable and intelligent man.”

Sean Farmar Sean Farmar, Chief Technical Architect at Candidate Manager Ltd
“Udi has provided us with guidance in system architecture and supports our implementation of NServiceBus in our core business application.

He accompanied us in all stages of our development cycle and helped us put vision into real life distributed scalable software. He brought fresh thinking, great in depth of understanding software, and ongoing support that proved as valuable and cost effective.

Udi has the unique ability to analyze the business problem and come up with a simple and elegant solution for the code and the business alike.
With Udi's attention to details, and knowledge we avoided pit falls that would cost us dearly.”

Børge Hansen Børge Hansen, Architect Advisor at Microsoft
“Udi delivered a 5 hour long workshop on SOA for aspiring architects in Norway. While keeping everyone awake and excited Udi gave us some great insights and really delivered on making complex software challenges simple. Truly the software simplist.”

Motty Cohen, SW Manager at KorenTec Technologies
“I know Udi very well from our mutual work at KorenTec. During the analysis and design of a complex, distributed C4I system - where the basic concepts of NServiceBus start to emerge - I gained a lot of "Udi's hours" so I can surely say that he is a professional, skilled architect with fresh ideas and unique perspective for solving complex architecture challenges. His ideas, concepts and parts of the artifacts are the basis of several state-of-the-art C4I systems that I was involved in their architecture design.”

Aaron Jensen Aaron Jensen, VP of Engineering at Eleutian Technology
Awesome. Just awesome.

We’d been meaning to delve into messaging at Eleutian after multiple discussions with and blog posts from Greg Young and Udi Dahan in the past. We weren’t entirely sure where to start, how to start, what tools to use, how to use them, etc. Being able to sit in a room with Udi for an entire week while he described exactly how, why and what he does to tackle a massive enterprise system was invaluable to say the least.

We now have a much better direction and, more importantly, have the confidence we need to start introducing these powerful concepts into production at Eleutian.”

Gad Rosenthal Gad Rosenthal, Department Manager at Retalix
“A thinking person. Brought fresh and valuable ideas that helped us in architecting our product. When recommending a solution he supports it with evidence and detail so you can successfully act based on it. Udi's support "comes on all levels" - As the solution architect through to the detailed class design. Trustworthy!”

Chris Bilson Chris Bilson, Developer at Russell Investment Group
“I had the pleasure of attending a workshop Udi led at the Seattle ALT.NET conference in February 2009. I have been reading Udi's articles and listening to his podcasts for a long time and have always looked to him as a source of advice on software architecture.
When I actually met him and talked to him I was even more impressed. Not only is Udi an extremely likable person, he's got that rare gift of being able to explain complex concepts and ideas in a way that is easy to understand.
All the attendees of the workshop greatly appreciate the time he spent with us and the amazing insights into service oriented architecture he shared with us.”

Alexey Shestialtynov Alexey Shestialtynov, Senior .Net Developer at Candidate Manager
“I met Udi at Candidate Manager where he was brought in part-time as a consultant to help the company make its flagship product more scalable. For me, even after 30 years in software development, working with Udi was a great learning experience. I simply love his fresh ideas and architecture insights.
As we all know it is not enough to be armed with best tools and technologies to be successful in software - there is still human factor involved. When, as it happens, the project got in trouble, management asked Udi to step into a leadership role and bring it back on track. This he did in the span of a month. I can only wish that things had been done this way from the very beginning.
I look forward to working with Udi again in the future.”

Christopher Bennage Christopher Bennage, President at Blue Spire Consulting, Inc.
“My company was hired to be the primary development team for a large scale and highly distributed application. Since these are not necessarily everyday requirements, we wanted to bring in some additional expertise. We chose Udi because of his blogging, podcasting, and speaking. We asked him to to review our architectural strategy as well as the overall viability of project.
I was very impressed, as Udi demonstrated a broad understanding of the sorts of problems we would face. His advice was honest and unbiased and very pragmatic. Whenever I questioned him on particular points, he was able to backup his opinion with real life examples. I was also impressed with his clarity and precision. He was very careful to untangle the meaning of words that might be overloaded or otherwise confusing. While Udi's hourly rate may not be the cheapest, the ROI is undoubtedly a deal. I would highly recommend consulting with Udi.”

Robert Lewkovich, Product / Development Manager at Eggs Overnight
“Udi's advice and consulting were a huge time saver for the project I'm responsible for. The $ spent were well worth it and provided me with a more complete understanding of nServiceBus and most importantly in helping make the correct architectural decisions earlier thereby reducing later, and more expensive, rework.”

Ray Houston Ray Houston, Director of Development at TOPAZ Technologies
“Udi's SOA class made me smart - it was awesome.

The class was very well put together. The materials were clear and concise and Udi did a fantastic job presenting it. It was a good mixture of lecture, coding, and question and answer. I fully expected that I would be taking notes like crazy, but it was so well laid out that the only thing I wrote down the entire course was what I wanted for lunch. Udi provided us with all the lecture materials and everyone has access to all of the samples which are in the nServiceBus trunk.

Now I know why Udi is the "Software Simplist." I was amazed to find that all the code and solutions were indeed very simple. The patterns that Udi presented keep things simple by isolating complexity so that it doesn't creep into your day to day code. The domain code looks the same if it's running in a single process or if it's running in 100 processes.”

Ian Cooper Ian Cooper, Team Lead at Beazley
“Udi is one of the leaders in the .Net development community, one of the truly smart guys who do not just get best architectural practice well enough to educate others but drives innovation. Udi consistently challenges my thinking in ways that make me better at what I do.”

Liron Levy, Team Leader at Rafael
“I've met Udi when I worked as a team leader in Rafael. One of the most senior managers there knew Udi because he was doing superb architecture job in another Rafael project and he recommended bringing him on board to help the project I was leading.
Udi brought with him fresh solutions and invaluable deep architecture insights. He is an authority on SOA (service oriented architecture) and this was a tremendous help in our project.
On the personal level - Udi is a great communicator and can persuade even the most difficult audiences (I was part of such an audience myself..) by bringing sound explanations that draw on his extensive knowledge in the software business. Working with Udi was a great learning experience for me, and I'll be happy to work with him again in the future.”

Adam Dymitruk Adam Dymitruk, Director of IT at Apara Systems
“I met Udi for the first time at DevTeach in Montreal back in early 2007. While Udi is usually involved in SOA subjects, his knowledge spans all of a software development company's concerns. I would not hesitate to recommend Udi for any company that needs excellent leadership, mentoring, problem solving, application of patterns, implementation of methodologies and straight out solution development.
There are very few people in the world that are as dedicated to their craft as Udi is to his. At ALT.NET Seattle, Udi explained many core ideas about SOA. The team that I brought with me found his workshop and other talks the highlight of the event and provided the most value to us and our organization. I am thrilled to have the opportunity to recommend him.”

Eytan Michaeli Eytan Michaeli, CTO Korentec
“Udi was responsible for a major project in the company, and as a chief architect designed a complex multi server C4I system with many innovations and excellent performance.”

Carl Kenne Carl Kenne, .Net Consultant at Dotway AB
“Udi's session "DDD in Enterprise apps" was truly an eye opener. Udi has a great ability to explain complex enterprise designs in a very comprehensive and inspiring way. I've seen several sessions on both DDD and SOA in the past, but Udi puts it in a completly new perspective and makes us understand what it's all really about. If you ever have a chance to see any of Udi's sessions in the future, take it!”

Avi Nehama, R&D Project Manager at Retalix
“Not only that Udi is a briliant software architecture consultant, he also has remarkable abilities to present complex ideas in a simple and concise manner, and...
always with a smile. Udi is indeed a top-league professional!”

Ben Scheirman Ben Scheirman, Lead Developer at CenterPoint Energy
“Udi is one of those rare people who not only deeply understands SOA and domain driven design, but also eloquently conveys that in an easy to grasp way. He is patient, polite, and easy to talk to. I'm extremely glad I came to his workshop on SOA.”

Scott C. Reynolds Scott C. Reynolds, Director of Software Engineering at CBLPath
“Udi is consistently advancing the state of thought in software architecture, service orientation, and domain modeling.
His mastery of the technologies and techniques is second to none, but he pairs that with a singular ability to listen and communicate effectively with all parties, technical and non, to help people arrive at context-appropriate solutions. Every time I have worked with Udi, or attended a talk of his, or just had a conversation with him I have come away from it enriched with new understanding about the ideas discussed.”

Evgeny-Hen Osipow, Head of R&D at PCLine
“Udi has helped PCLine on projects by implementing architectural blueprints demonstrating the value of simple design and code.”

Rhys Campbell Rhys Campbell, Owner at Artemis West
“For many years I have been following the works of Udi. His explanation of often complex design and architectural concepts are so cleanly broken down that even the most junior of architects can begin to understand these concepts. These concepts however tend to typify the "real world" problems we face daily so even the most experienced software expert will find himself in an "Aha!" moment when following Udi teachings.
It was a pleasure to finally meet Udi in Seattle Alt.Net OpenSpaces 2008, where I was pleasantly surprised at how down-to-earth and approachable he was. His depth and breadth of software knowledge also became apparent when discussion with his peers quickly dove deep in to the problems we current face. If given the opportunity to work with or recommend Udi I would quickly take that chance. When I think .Net Architecture, I think Udi.”

Sverre Hundeide Sverre Hundeide, Senior Consultant at Objectware
“Udi had been hired to present the third LEAP master class in Oslo. He is an well known international expert on enterprise software architecture and design, and is the author of the open source messaging framework nServiceBus. The entire class was based on discussion and interaction with the audience, and the only Power Point slide used was the one showing the agenda.
He started out with sketching a naive traditional n-tier application (big ball of mud), and based on suggestions from the audience we explored different solutions which might improve the solution. Whatever suggestions we threw at him, he always had a thoroughly considered answer describing pros and cons with the suggested solution. He obviously has a lot of experience with real world enterprise SOA applications.”

Raphaël Wouters Raphaël Wouters, Owner/Managing Partner at Medinternals
“I attended Udi's excellent course 'Advanced Distributed System Design with SOA and DDD' at Skillsmatter. Few people can truly claim such a high skill and expertise level, present it using a pragmatic, concrete no-nonsense approach and still stay reachable.”

Nimrod Peleg Nimrod Peleg, Lab Engineer at Technion IIT
“One of the best programmers and software engineer I've ever met, creative, knows how to design and implemet, very collaborative and finally - the applications he designed implemeted work for many years without any problems!

Jose Manuel Beas
“When I attended Udi's SOA Workshop, then it suddenly changed my view of what Service Oriented Architectures were all about. Udi explained complex concepts very clearly and created a very productive discussion environment where all the attendees could learn a lot. I strongly recommend hiring Udi.”

Daniel Jin Daniel Jin, Senior Lead Developer at PJM Interconnection
“Udi is one of the top SOA guru in the .NET space. He is always eager to help others by sharing his knowledge and experiences. His blog articles often offer deep insights and is a invaluable resource. I highly recommend him.”

Pasi Taive Pasi Taive, Chief Architect at Tieto
“I attended both of Udi's "UI Composition Key to SOA Success" and "DDD in Enterprise Apps" sessions and they were exceptionally good. I will definitely participate in his sessions again. Udi is a great presenter and has the ability to explain complex issues in a manner that everyone understands.”

Eran Sagi, Software Architect at HP
“So far, I heard about Service Oriented architecture all over. Everyone mentions it – the big buzz word. But, when I actually asked someone for what does it really mean, no one managed to give me a complete satisfied answer. Finally in his excellent course “Advanced Distributed Systems”, I got the answers I was looking for. Udi went over the different motivations (principles) of Services Oriented, explained them well one by one, and showed how each one could be technically addressed using NService bus. In his course, Udi also explain the way of thinking when coming to design a Service Oriented system. What are the questions you need to ask yourself in order to shape your system, place the logic in the right places for best Service Oriented system.

I would recommend this course for any architect or developer who deals with distributed system, but not only. In my work we do not have a real distributed system, but one PC which host both the UI application and the different services inside, all communicating via WCF. I found that many of the architecture principles and motivations of SOA apply for our system as well. Enough that you have SW partitioned into components and most of the principles becomes relevant to you as well. Bottom line – an excellent course recommended to any SW Architect, or any developer dealing with distributed system.”

Consult with Udi

Guest Authored Books

Creative Commons License  © Copyright 2005-2011, Udi Dahan. email@UdiDahan.com