Skip to main content

A Lotta Architecture - A Reply to "A Little Architecture"

A recent post about architecture from Uncle Bob got me thinking and talking about a typical day in the life of a developer. It's well worth a read. In fact at the time of writing this reply there are 347 retweets and 288 likes - of which I was one of those statistics.

The advice is practical and advice that I agree with. Except this is not the full story. While deferring architectural decisions as late as possible is a good thing, such details actually tend to be the most important, costly and difficult parts of an application.

In the example the BusinessRuleGateway allows the business logic to be coded in pure isolation, using a stub or fake. This is fantastic and provides numerous benefits. Sadly the actual implementation of the gateway requires knowledge of MySql. This may be obvious but the decision of what database to use cannot be deferred or ignored forever.

Once chosen you will require intricate knowledge of how it works and is implemented. When things go wrong and you are staring at a one hundred line stack trace, you better hope you understand how the DB is configured.

Additionally the gateway interface demonstrates another common problem, leaky abstractions. This particular interface while coded without an implementation in mind, is tightly coupled to a relational database. If we opted for a file system or document database the use of transactions is now incorrect.

From my experience such implementation details end up taking the majority of your time and effort - see the 80/20 rule. From small to large systems, this tends to be a common running theme.

  • One project was tightly coupled to the web framework. Making a code change required detailed knowledge of the inner workings of the page request/response lifecycle.
  • Another required deep knowledge, awareness and fear of the legacy database schema. Code changes were easy. Plugging in a legacy database took horrific amounts of effort.
  • A current project is working with an asynchronous, distributed system. In order to be productive a solid understanding of the mechanics of message queues and distributed computing is required.

In some of these cases, the advice offered around abstracting implementation details was actually used. Rarely is the problem ever pure business logic. In a typical week I would bet a large sum of money the majority of developers find themselves fighting with integration, or third party dependencies, over faulty domain logic.

Deferring decisions is a sign of good architecture, but the act of deferral or hiding behind interfaces only gets you so far. The sad state of affairs is that any implementation detail left unchecked can swallow applications in complexity.


Popular posts from this blog

Three Steps to Code Quality via TDD

Common complaints and problems that I've both encountered and hear other developers raise when it comes to the practice of Test Driven Development are: Impossible to refactor without all the tests breakingMinor changes require hours of changes to test codeTest setup is huge, slow to write and difficult to understandThe use of test doubles (mocks, stubs and fakes is confusing)Over the next three posts I will demonstrate three easy steps that can resolve the problems above. In turn this will allow developers to gain one of the benefits that TDD promises - the ability to refactor your code mercifully in order to improve code quality.StepsStop Making Everything PublicLimit the Amount of Dependencies you Use A Unit is Not Always a Method or ClassCode quality is a tricky subject and highly subjective, however if you follow the three guidelines above you should have the ability to radically change implementation details and therefore improve code quality when needed.

DRY vs DAMP in Tests

In the previous post I mentioned that duplication in tests is not always bad. Sometimes duplication becomes a problem. Tests can become large or virtually identically excluding a few lines. Changes to these tests can take a while and increase the maintenance overhead. At this point, DRY violations need to be resolved.SolutionsTest HelpersA common solution is to extract common functionality into setup methods or other helper utilities. While this will remove and reduce duplication this can make tests a bit harder to read as the test is now split amongst unrelated components. There is a limit to how useful such extractions can help as each test may need to do something slightly differently.DAMP - Descriptive and Meaningful PhrasesDescriptive and Meaningful Phrases is the alter ego of DRY. DAMP tests often use the builder pattern to construct the System Under Test. This allows calls to be chained in a fluent API style, similar to the Page Object Pattern. Internally the implementation wil…

Coding In the Real World

As a student when confronted with a problem, I would end up coding it and thinking - how do the professionals do this?For some reason I had the impression that once I entered the industry I would find enlightenment. Discovering the one true way to write high quality, professional code.It turns out that code in industry is not too far removed from the code I was writing back when I knew very little.Code in the real world can be:messy or cleanhard or easy to understandsimple or complexeasy or hard to changeor any combination of the aboveVery rarely will you be confronted with a problem that is difficult. Most challenges typically are formed around individuals and processes, rather than day to day coding. Years later I finally have the answer. Code in the real world is not that much different to code we were all writing when we first started out.If I could offer myself some advice back in those early days it would be to follow KISS, YAGNI and DRY religiously. The rest will fall into plac…

Feature Toggles

I'm a fan of regular releasing. My background and experience leads me to release as regularly as possible. There are numerous benefits to regular releases; limited risk, slicker release processes and the ability to change as requirements evolve.The problem with this concept is how can you release when features are not functionally complete?SolutionIf there is still work in progress, one solution to allow frequent releases is to use feature toggles. Feature toggles are simple conditional statements that are either enabled or disabled based on some condition.This simple example shows a feature toggle for an "Edit User" feature. If the boolean condition is false, then we only show the "New User" feature and the "Admin" feature. This boolean value will be provided by various means, usually a configuration file. This means at certain points we can change this value in order to demonstrate the "Edit User" functionality. Our demo environment could …

Reused Abstraction Principle

This is the second part of my series on abstractions.Part 1 - AbstractionsPart 3 - Dependency Elimination PrincipleThe Reused Abstraction Principle is a simple in concept in practice, but oddly rarely followed in typical enterprise development. I myself have been incredibly guilty of this in the past.Most code bases have a 1:1 mapping of interfaces to implementations. Usually this is the sign of TDD or automated testing being applied badly. The majority of these interfaces are wrong. 1:1 mappings between interfaces and implementations is a code smell.Such situations are usually the result of extracting an interface from an implementation, rather than having the client drive behaviour.These interfaces are also often bad abstractions, known as "leaky abstractions". As I've discussed previously, these abstractions tend to offer nothing more than simple indirection.ExampleApply the "rule of three". If there is only ever one implementation, then you don't need …