Monolithic vs scalable Angular architectures
Maintaining everything under control is more than hard...in the case of monolithic architecture, it’s almost impossible. To maintain all these under control, a scalable architecture is almost compulsory.
The architecture should respect the following goals:
- To maintain or even improve speed (velocity)
- To ease the implementation of new requirements
- To maintain the application’s performance
Without implementing this sort of architecture, in the beginning, an application may develop very quickly and the requirements may be implemented easily. Problems usually appear during the development.
FOR A MONOLITHIC ARCHITECTURE
As the requirements get more difficult to implement, the time spent on them becomes higher and higher. All changes involve modifying other functionalities that in the end lead to regressions. Also, mentality, it’s harder for the developers to confront with the influx of information and especially of changes. You get to a point where you don’t see the light at the end of the tunnel and the speed of development keeps on constantly diminishing.
IN THE CASE OF A SCALABLE ARCHITECTURE:
A scalable architecture makes the development speed to remain almost the same throughout the development cycle. At the beginning of the development cycle, the speed will seem lower, but the advantage is that it will be constant. Remember the fable of the hare and the tortoise...it’s the same thing in the case of architectures. Small hint, a scalable architecture is a tortoise.
To get back to our story, the scalable architecture gives us better control of the project, a more accurate planning, and a high-quality and performance at any point of development.
Keep in mind that an Angular scalable architecture needs to go through the following principles:
- Abstraction Layers
- Smart & Dumb Components
- Unidirectional data flow
For further details, also read Angular architecture and specific layers and Angular: Evolving towards a Scalable Architecture
References:
