Frontend architecture refers to the structure and organization of the client-side part of a web application and converting the architectural drivers into a technical solution, technical roadmap, communicating the vision to a number of stakeholders both inside and outside the software development team, and introducing the technical leadership.
"Architecture" typically refers to the high-level structural decisions that have a significant impact on the system and are difficult to change once made. On the other hand, "design" encompasses the detailed decisions and implementations that are more flexible and can be adjusted without major consequences.
- Functional Requirements: The technical functions that represent the main product features. These functions describe how the system behaves and what it should do.
- Quality Attributes: Quality Attributes are a set of criteria that describe how a software system should behave and perform rather than specifying specific functionalities or features.
- Constraints: Constraints can encompass various factors, such as technical limitations, resource constraints, or environmental considerations.
- Principles: The Standards or the Guidelines that should be applied while implementing and creating the Frontend solution.
- Book: Software Architecture for Developers by @simonbrown
- Book: Frontend Architecture for Design System by Micah Godbolt
- Youtube: GOTO Conferences