Software Architecture Using Angular

Angular has grown steadily more popular since itsrelease, and agrowingnumberofbooks are nowavailable to teach programmers how to use it. But building anapplication involves a lot more than just writing code: in order to beperformant and maintainable, the application must have someover-arching architectural plan that ties its pieces together andgives direction to future growth.

To help with this, Rangle has started to assemble aguide to software architecture using Angular. How should sets ofcomponents be organized so that they can easily be tested and re-used?How can Angular be combined with tools like Redux to simplify statemanagement in an asynchronous, event-driven world? How can we designtoday to make server-side rendering less painful to add tomorrow (andshould we be doing SSR at all)? Sooner or later, every growingapplication has to wrestle with these issues; our aim is to distillexpert knowledge so that people can make the right decisions early on.

The first chapter of this new guide, based on work by DanielFigueiredo and Renee Vrantsidis, is now available. We would begrateful for feedback on its content and format, and for suggestionsabout other topics the community would like to see covered. And ifyou are interested in contributing, please get intouch: as always, we are smarter together than anyone of us is alone.

Be the first to know when we release the next chapter of the Architect’s Guide to Angular.

原文: https://angular-2-training-book.rangle.io/handout/architect/