Change how you think about designing software systems

The Fallacies of Distributed Computing were formalized nearly 20 years ago and, despite the passage of time and advances in technology, the principles behind them still hold true. What’s more, falling prey to the fallacies can cause even more damage today because of the size and scope of the systems we build.

The course -- led by one of the world’s foremost experts on distributed systems -- will show you how to recognize and avoid the mistakes that still plague how developers design systems today.

  • 1

    Fallacy #1: The network is reliable

    • Fallacy #1: The network is reliable

    • The best way to build distributed systems

  • 2

    Fallacy #2: Latency is zero

    • Fallacy #2: Latency is zero

  • 3

    Fallacy #3: Bandwidth is infinite

    • Fallacy #3: Bandwidth is infinite

  • 4

    Fallacy #4: The network is secure

    • Fallacy #4: The network is secure

  • 5

    Fallacy #5: Topology doesn't change

    • Fallacy #5: Topology doesn't change

  • 6

    Fallacy #6: There is one administrator

    • Fallacy #6: There is one administrator

  • 7

    Fallacy #7: Transport cost is zero

    • Fallacy #7: Transport cost is zero

  • 8

    Fallacy #8: The network is homogeneous

    • Fallacy #8: The network is homogeneous

  • 9

    About the ADSD Course

    • About the ADSD course

About the instructor

The software simplist

Udi Dahan

Udi Dahan is one of the world’s foremost experts on Service-Oriented Architecture, Distributed Systems and Domain-Driven Design. He's also the creator of NServiceBus, the most popular service bus for .NET.

Sign up and start thinking about designing software systems in a new way