6 Comments
User's avatar
Nwakpa Ejike Chukwuma's avatar

This is a masterpiece. I'll suggest that a part 2 is done for this and this time a video explaining this with real-time production ready project is the central means of communicating this. I hope you subscribe to your YouTube channel if there's any too.

Paul Iusztin's avatar

Thanks 🙏 So far, no YouTube channel, but I plan start doing videos this year. Will consider your suggestion!

Meenakshi NavamaniAvadaiappan's avatar

Thanks for the good 😊

Esther Dawes's avatar

Hello, do you have an example project that follows this?

Daniel Kaesmayr's avatar

I’ve been using architecture tests that enforce the folder structure, and clean architectural import direction.

Grzegorz's avatar

Strong piece — the "layers as virtual concepts" framing is the part most people miss. One thing I'd add from building a stateful agent with persistent memory: the orchestrator is where the four layers legitimately converge, and not all of that coupling is accidental. I tried slicing mine into clean seams once and ended up with five files plus a callback graph I had to hold in my head all at once — strictly worse than one dense-but-readable module. Sometimes the pragmatic move is to accept essential coupling at the composition point and decouple only the leaves. Which is really just your point #3 taken to its conclusion.