Replacing grown systems without downtime
In practice we keep seeing the same mistake again and again. A case from the last few months makes it concrete. The first idea is understandable, but it usually ends up costing…
Latest news
Monolith or services: what actually decides it
It takes longer, but it can be reversed at any point. The first idea is understandable, but it usually ends up costing more. The instinct is understandable, but it rarely works…
Services or monolith: the question is usually wrong
It looks slower, but it stays predictable. We work in small steps instead: survey first, then change. It takes longer, but it stays predictable. An example from a recent project…
Why full rewrites fail so often
It takes longer, but it stays predictable. We proceed incrementally: survey first, then rebuild. A case from a recent project shows this…
A second opinion before signing: when it pays off
On projects we run into the same mistake again and again. In practice we run into the same mistake again and…
Data migration: plan B is the part that matters
The instinct is understandable, but it rarely works out. It looks slower, but it can be reversed at any point. An example from the last few months makes it concrete. In practice…
Monitoring: the minimum that helps
It looks slower, but it stays predictable. The instinct is understandable, but it rarely works out. An example from a recent project shows this…