TagArchitecture

Software Architecture is more than Boxes and Arrows

S

I watch many software architecture talks (on-site and virtually), and I am starting to think that my understanding of software architecture differs from that of most speakers. I see a lot of talking about bounded contexts (as in Domain Driven Design), layers (as in Clean /Hexagonal/Onion Architecture), and dependencies (between classes, up-stream/down-stream contexts). Don’t get me wrong; these concepts are important. However, they are just a small part of all the aspects a software...

Evolution of Software Architectures

E

Evolutionary software architecture has gained much traction lately—at least in my bubble. It is one of my favourite topics, and I have presented and conducted workshops on it for over a decade. So, let me add a thought to the discussion:

The evolution of a software architecture has three dimensions:

Technical evolution,

conceptual evolution, and

the evolution of business capabilities

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

B

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

T

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

L

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...

Recent Posts