Book review: Lean Architecture – for Agile Software Development by Jamey O. Coplien & Gertrud Bjornvig


Target audience: software architects Urs’ comment: This book claims a lot, and delivers little. There are several good tips in this book, but overall I simply don’t like it. I don’t like the “tone” it is written in. There are only few books about Agile and Lean software architecture, therefore I cannot really give a better alternative covering the same topic. Ultimately,  that means you have to read it in case you are in any kind responsible for the architecture in...

The buzz around microservices


The term microservices has been humming around in the industry quite a long time now. Several articles and videos have been posted. People have been arguing about whether their services are true microservices or not on twitter and other social media streams. Lately Martin Fowler published an article about microservices which quickly led to discussions, flamewars and a lot of blog posts about this topic. Here is my personal opinion about the microservices architecture style. You have the right...

Logging in an onion architecture


In reaction to this post I received an interesting comment from valeriu. A very nice wrap-up about onion architecture, thank you for sharing the presentation! However, there’s a something that’s bothering me. Sometimes, you may have need to interact with some infrastructure parts from the inner layers. A good example will be logging – domain service may need to log some details or exceptions. How you would approach that? To keep the right direction for dependencies (if you’re really committed...

Chop onions instead of layers


This is the presentation handout for a presentation I gave at the bbv Techday 2013. Special thanks to Jeffrey Palermo for supporting me.  Chopping onions usually makes you cry. This is not the case in software architecture. In contrary! The onion architecture, introduced by Jeffrey Palermo, puts the widely known layered architecture onto its head. Get to know the onion architecture and its merits with simple and practical examples. Combined with code structuring by feature your software is easy...

Structure your code by feature


cross-post from bbv blog
When software projects grow both in age and size the developers often struggle with the structure of the code. It gets more and more difficult to find the class you have to change for a new requirement. In this post, I’ll show you how we organize our code and how we derive our structure directly from the requirements.

Presentation: Agile Code Design – how to keep your code flexible


These are the slides along with some comments from a presentation I gave lately in the bbv .Net System boot camp – the yearly education week of my division in my company. Once upon a time, Agile Software development came to our software development country. Like a monster, Agile software methodologies scared the hell out of us. Suddenly, we had to find ways how to build software so that we could keep up with the high rate of change, just-in-time requirements and a sacrificial offering – a...

Clean Code and Clean TDD Cheat Sheets


Updated: new version here! I have compiled two cheat sheets about clean code (the ones mentioned in my post about Code Quality!). The first covers clean code – code that is easy readable and keeps changeable. The second is about Test Driven Development. Both cheat sheets list principles, patterns, practices and smells. You can download them here – Clean Code Cheat Sheet V1.3, Clean TDD Cheat Sheet V1.2. Take a look! I’d like to read your feedback in the comments section… (just an...

Recent Posts