Enterprise RAG Architecture: From Search to a Knowledge Platform
How to design scalable RAG for many data sources, millions of documents, and access-controlled enterprise knowledge.
Yevhen Stuzhuk - Personal Portfolio
I am a Senior Software Engineer
← All posts
Tag
architecture
All blog posts with this tag.
Designing an Enterprise AI Platform: From Pilot to Standard
How to design a scalable enterprise AI platform where knowledge, security, and integrations matter more than any individual model.
Enterprise Assessment: Start an AI Project with Facts
How interviews, process analysis, and knowledge discovery prepare an enterprise AI project for sound design.
An Enterprise AI Architect’s First Day: Start with the Business
Why an enterprise AI project starts with business needs, knowledge, and security—not with a model or server choice.
The Future of Enterprise AI: Architecture That Lasts
How to build an enterprise AI platform that can outlive changing models, vendors, and data formats.
Where Code Generation Ends and Engineering Begins
AI already writes working functions, but a product is architecture, context, risk, and accountability. The boundary between code and engineering, a 15-year legacy case study, and developer skills in 2026.
Can AI Understand a Codebase With 15 Years of History?
Millions of lines, hundreds of tables, dozens of integrations: what AI grasps in hours, where it fails, how teams deploy RAG and repo indexing, and why expert + model beats either alone.
How the Modern Web Works: From Browser to Database
The full HTTP request journey — DNS, TLS, CDN, load balancer, Nginx, backend, Redis, queues, PostgreSQL, and back to the browser. A practical guide for developers and architects.
How to Design a Modern ERP System in 2026: From Monolith to Platform
Metadata Driven Architecture, platform engines, frontend stack, and migration strategy — how to build an ERP that evolves for decades without a rewrite every five years.
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.
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.