Why did we choose Angular?
A year ago, when PLATA was just born, we faced the first problem during a discussion about the web — what kind of frameworks we would like to use to build a new digital bank in Mexico. Of course, we had requirements for the framework. The time has come for modern and progressive SSR-first frameworks. We call them meta-frameworks. And the most significant part of them are not based on Angular. But why did we pick Angular? I'll get the answer for you.
What do we do?
PLATA is a digital financial services and technology company. We want to be a big enterprise with countless services and applications using our design system, best practices, infrastructure solutions, and incredibly skilled teams.
What do we need?
Performance. The framework must be productive and fast. In an ideal world, it has to have good numbers in this benchmark.
Security. The framework should include protection against common security threats to front-end applications.
Tooling and DX. The framework should have a CLI (or something) to simplify development. Developers don't have to worry about building, linting, formatting, etc.
Compatibility and integration. The framework should easily integrate with other systems and technologies used in the company.
