About
The person and the thinking behind Architecture Log.
Hi — I'm Filip, a software and solution architect. Architecture Log is where I write down the reasoning behind the systems I design, build, and review: the patterns that earn their keep, the trade-offs that are easy to miss, and the decisions that look obvious only in hindsight.
The goal is practical depth over hot takes. Every article aims to be the explanation I wish I'd had when I first hit the problem — concrete, honest about the downsides, and useful whether you're sketching a new system or untangling an old one.
What you'll find here
- System design — scoping, service boundaries, and scaling, with the trade-offs made explicit.
- Architecture patterns — hexagonal, event-driven, CQRS, layered: when each pays off and when it quietly costs you.
- Solution architecture — turning real requirements and constraints into systems that hold up in production.
Get in touch
The best place to reach me — or to follow what I'm working on — is LinkedIn. You can also subscribe via the RSS feed.