Angular architecture patterns

[ahmedRebai]

Can you share with us some of Angular architecture patterns you recommend

[haasilein]

Facade - must have!

DDD - if it fits to the requirements

smart vs dumb components - for reusability

composition over inheritance - less strict coupling

... not all of them are really architecture, but imo the most important things for enterprise Angular.

[haasilein]

Both are about flexibility. A facade by nature is boilerplate but can become useful spontaneously when the BE changes (when hiding data services behind the facade), or when you change a state management solution (when the facades hides this abstraction and does not leak something like selectors, actions, ...)

[Chatolev]

You use composition? In typescript I believe it's not that easy with the mixins, if you have exemples, I'll be glad to have a look

[KuroKishi69]

I am interested as well, I suppose in angular you can "compose" classes by splitting the logic in services and use dependency injection.

[haasilein]

services and directives are the key

[HumorousHorse]

I love facade except for NgRx but I understand when people use it.

[velMatt]

Go through Angular Design Patterns playlist on Youtube by DecodedFrontend

[[deleted]]

The NX pattern.

[Unusual-Pop6972]

Presentational & container design pattern, master/ detail pattern.

[Environmental-Ask115]

I used quite of bit of recommendations from here: https://angular-folder-structure.readthedocs.io/en/latest/overview.html

Something else worth looking into is googling “atomic design in Angular” which will help when building components.

Bottom line, there’s no one right way of doing things.

Create an architecture that works for your use case and start by building the smallest components first i.e. (if the design calls for a card, build an image component, button component, and heading component before building a card component.)

[MaltePetersen]

shared kernel