Angular is built on components. We initialize an app by bootstrapping a component. We use components to encapsulate functionality, markup, and style. We route to components. But are we too quick to “componentize all the things”? Sure, a new component is a selector and a template away, but should we be so quick to create components every chance we get? Is it worth paying the “component tax”?

Angular is not just about building with components. It’s about understanding how to architect with components. When to create decision making components and when to make presentational components. When to choose constructor injected services and when to go with an application state approach. And it’s about understanding the hidden prices we pay for going with these different decisions.

During this talk we will journey through the architecture decisions, we face when building with components and find balance as we gain a better understanding of the synergy that is possible when we learn how to embrace component tranquility.