10. It’s too expensive
$2,500 is way too much to pay for a one week training course with 50 or so other people. Besides, you don’t even get a t-shirt.
9. You want detailed implementation advice
If you want to see lots of code samples and hands-on coding, this is not the place for you. If you have a laptop, leave it at home or at least in the trunk of your car. You’re not going to need it. Instead, bring an open mind.
8. You like to surf the Internet during the “boring parts”.
Parts of the lecture can seem a little dry especially if you figure Udi is just setting the stage for the good CQRS implementation stuff coming later. Unfortunately, if you tune out for more than a few seconds, the odds are you’re going to miss something pretty important. If you want to pretend to take notes on your laptop, that’s fine. However, as Udi points out, it’s better to take notes with an old-fashioned pen and paper.
7. You are a DBA
If you break your distributed system into small, autonomous components, you really don’t need a centralized database. Udi utters this heresy more than once. To make matters worse, he says the database is a black hole of undesirable coupling. Do I need to say more?
6. You are a senior programmer, distinguished engineer, application architect or any other kind of lofty programmer that prides himself on writing clever code
If you break a distributed system into small, autonomous components, code gets simpler. We’re talking methods with two lines of code. We’re talking projects with a single class. You could write this stuff in straight Basic without much worry. No tests, no big problem. Poor implementations can be corrected in a few minutes. Even maintenance programmers can understand the code! There are a couple of juicy bits that require an expert, but fewer than you think. Did I mention that code gets much simpler?
5. You are the go-to guy for distributed caching
Have you ever saved the day with an in-process cache or even a distributed cache? Well, Udi shows you where you went wrong and how you could have done it much better by letting the Internet do the work for you.
4. You believe in implementing “best practices”
Udi shows you why there is no such thing as a best practice. He gives you plenty of examples that will help you understand that it really always depends; You should use the simplest possible approach that meets the real requirements.
3. You dig monster trucks and like to go mudding on the weekend
If you love code reuse, centralized OO domain models, ORMs like NHibernate and centralized databases with perfect relational integrity, you probably don’t want to go to this class. Udi will show you how these seemingly desirable things can help you turn your system into a big ball of mud.
2. You want to “do CQRS” in your next system
Udi spends a long time telling you all the reasons you don’t need CQRS. He even says it is neither a “best practice” nor a top-level architectural pattern. Hasn’t this guy heard the distributed podcast?
1. You want Udi to bless the architecture of your latest project
Unless you’ve gone to the course before, I doubt you’ll come out of it feeling good about everything in your latest system. You will feel dumb at times. Whatever you do, don’t bring your boss!
If you want to learn more about what the course is like, you might want to read my series of impressions.