How to Design a System That Will Last 10 Years
Why systems die from early architectural decisions, not outdated tech — and how to design for change, not features: module boundaries, domain modeling, data, ADRs, and a decade-long checklist.
Yevhen Stuzhuk - Personal Portfolio
I am a Senior Software Engineer
← All posts
Tag
architecture
All blog posts with this tag.
-
-
Why EAV Looks Like a Good Idea — Then Destroys ERP Performance
Entity–Attribute–Value looks perfect at the start: flexibility without migrations. Why JOINs, indexes, and reports break ERP years later — and where EAV fits, and where it does not.
-
The Most Expensive Mistake in ERP Architecture — Trying to Make the System Universal
Why the illusion of universality turns ERP into an EAV monster: lost performance, typing, and business meaning — and how to build around the domain, not abstract entities.
-
Evolution of Web Application Architecture Over the Last 20 Years
From server-side rendering in 2005 to AI apps and edge computing: how web architectures changed, why past choices were not mistakes, and how to pick an approach in 2026.
-
Why Most ERP Systems Turn Into Monolithic Monsters
The ERP success paradox: exceptions, technical debt, a single database, and the distributed monolith. Why the monster follows business growth and how to slow decay.