In 2024, Angular keeps changing for better with ever increasing pace, but the big picture remains the same which makes architecture know-how timeless and well worth your time!
Hey there folks! The Angular renaissance continues, and it’s going even stronger in 2024 with Angular team delivering amazing things like Signal based inputs / outputs / viewChild(ren) / contentChild(ren), new control flow, @defer for seamless component lazy loading all the way to the zone-less change detection which was released in preview in Angular 18 in May!
These new APIs, syntaxes and approaches are amazing and have demonstrably positive impact on the developer experience, performance and the quality of the codebases!
BUT
At the same time, they don’t really have much impact on the way we structure our applications and workspaces. And that’s a great thing because…
Angular architecture focused know-how is basically timeless and well worth spending time on!
The way we structure and architect our Angular application stayed virtually the same from the times of ancient Angular 4 which brought us stable Router implementation with support for lazy loaded routes which is one of the most important building blocks of clean architecture (not just performance) until today!
Of course, there have been some API adjustments over time, but they mostly had effect on the more low (syntax) level instead of completely changing the way we’re doing things!
The best example to illustrate this point is the advent of the standalone components and APIs which made NgModules optional. The impact of this change is that instead of lazy loading of feature modules, we’re now lazy loading feature route configs (or root feature components).
Is it a difference? Sure!
Does it change how things are organized and structured on the higher architectural level ? NOT AT ALL!
I hope this introduction sets the tone and spiked your curiosity to learn more about Angular architecture as such know-how was, is and will stay relevant and useful! It will allow you to ensure success of your projects and provide value for you, your team and the organization you work for!
So what are the most common mistakes in the context of Angular application architecture?
Top comments (1)
I was expecting numbered sections that show a clear concise discussion..... not a half essay to find these 10 items and then to be then rerouted to another website.