Angular (aka Angular 2, 4, 5, 6...) is a new framework completely rewritten from the ground up, replacing the now well-known AngularJS framework (aka Angular 1.x).
More that just a framework, Angular should now be considered as a whole platform which comes with a complete set of tools, like its own CLI, debug utilities or performance tools.
Angular has been around for some time now, but I still get the feeling that it’s not getting the love it deserved, probably because of other players in the field like React or VueJS. While the simplicity behind these frameworks can definitely be attractive, they lack in my opinion what is essential when making big, enterprise-grade apps: a solid frame to lead both experienced developers and beginners in the same direction and a rational convergence of tools, patterns and documentation. Yes, the Angular learning curve may seems a little steep, but it’s definitely worth it.
If you're new to Angular you may feel overwhelmed by the quantity of new concepts to apprehend, so before digging into this project you may want to start with this progressive tutorial that will guide you step by step into building a complete Angular application.
If you come from AngularJS and want to dig straight in the new version, you may want to take a look at the AngularJS vs 2 quick reference.
Until you know the full Angular API by heart, you may want to keep this cheatsheet that resumes the syntax and features on a single page at hand.
This project follows the standard Angular style guide.
More that just coding rules, this style guide also gives advices and best practices for a good application architecture and is an essential reading for starters. Reading deeper, you can even find many explanations for some design choices of the framework.
There is a lot to dig in Angular and some questions frequently bother people. In fact, most of unclear stuff seems to be related to modules, for example the dreaded "Core vs Shared modules" question.
The guys at Angular may have noticed that since you can now find a nice FAQ on their website answering all the common questions regarding modules. Don't hesitate to take a look at it, even if you think you are experienced enough with Angular 😉.
Even though they are not mandatory, Angular was designed for the use of design patterns you may not be accustomed to, like reactive programming, unidirectional data flow and centralized state management.
These concepts are difficult to resume in a few words, and despite being tightly related to each other they concern specific parts of an application flow, each being quite deep to learn on its own.
You will essentially find here a list of good starting points to learn more on these subjects.
You may not be aware of it, but Angular is now a reactive system by design. Although you are not forced to use reactive programming patterns, they make the core of the framework and it is definitely recommended to learn them if you want to leverage the best of Angular.
Angular uses RxJS to implement the Observable pattern.
An Observable is a stream of asynchronous events that can be processed with array-like operators.
While AngularJS used to rely heavily on Promises to handle asynchronous events, Observables are now used instead in Angular. Even though in specific cases like for HTTP requests, an Observable can be converted into a Promise, it is recommended to embrace the new paradigm as it can a lot more than Promises, with way less code. This transition is also explained in the Angular tutorial. Once you have made the switch, you will never look back again.
-
What is reactive programming?, explained nicely through a simple imaged story (5 min)
-
The introduction to reactive programming you've been missing, the title says it all (30 min)
-
Functional reactive programming for Angular 2 developers, see the functional reactive programming principles in practice with Angular (15 min)
-
RxMarbles, a graphical representation of Rx operators that greatly help to understand their usage
In opposition with AngularJS where one of its selling points was two-way data binding which ended up causing a lot of major headaches for complex applications, Angular now enforces unidirectional data flow.
What does it means? Said with other words, it means that change detection cannot cause cycles, which was one of AngularJS problematic points. It also helps to maintain simpler and more predictable data flows in applications, along with substantial performance improvements.
Wait, then why the Angular documentation have mention of a two-way binding syntax?
If you look closely, the new two-way binding syntax is just syntactic sugar to combine two one-way bindings (a property and event binding), keeping the data flow unidirectional.
This change is really important, as it was often the cause of performance issues with AngularJS, and it one of the pillars enabling better performance in new Angular apps.
While Angular tries to stay pattern-agnostic and can be used with conventional MV* patterns, it was designed with reactive programming in mind and really shines when used with reactive data flow patterns like redux, Flux or MVI.
As applications grow in size, keeping track of the all its individual components state and data flows can become tedious, and tend to be difficult to manage and debug.
The main goal of using a centralized state management is to make state changes predictable by imposing certain restrictions on how and when updates can happen, using unidirectional data flow.
This approach was first made popular with React with introduction of the Flux architecture. Many libraries emerged then trying to adapt and refine the original concept, and one of these gained massive popularity by providing a simpler, elegant alternative: Redux.
Redux is at the same time a library (with the big R) and a design pattern (with the little r), the latter being framework-agnostic and working very well with Angular.
The redux design pattern is based on these 3 principles:
- The application state is a single immutable data structure
- A state change is triggered by an action, an object describing what happened
- Pure functions called reducers take the previous state and the next action to compute the new state
The core concepts behind these principles are nicely explained in this example (3 min).
For those interested, the redux pattern was notably inspired by The Elm Architecture and the CQRS pattern.
You can make Angular work with any state management library you like, but your best bet would be to use NGXS or @ngrx. Both works the same as the popular Redux library, but with a tight integration with Angular and RxJS, with some nice additional developer utilities.
NGXS is based on the same concepts as @ngrx, but with less boilerplate and a nicer syntax, making it less intimidating.
Here are some resources to get started:
-
Angular NGXS tutorial with example from scratch, a guided tutorial for NGXS (10 min)
-
Build a better Angular 2 application with redux and ngrx, a nice tutorial for @ngrx (30 min)
-
Comprehensive introduction to @ngrx/store, an in-depth walkthrough to this library usage in Angular (60 min)
You may have noticed that the starter template does not include a centralized state management system out of the box. Why is that? Well, while there is many benefits from using this pattern, the choice is ultimately up to your team and what you want to achieve with your app.
Keep in mind that using a single centralized state for your app introduces a new layer a complexity that might not be needed, depending of your goal.
While the new Angular version resolves by design most of the performance issues that could be experienced with AngularJS, there is always room for improvements. Just keep in mind that delivering an app with good performance is often a matter of common sense and sane development practices.
Here is a list of key points to check for in your app to make sure you deliver the best experience to your customers.
After going through the checklist, make sure to also run an audit of your page through Lighthouse, the latest Google tool that gives you meaningful insight about your app performance, accessibility, mobile compatibility and more.
Angular development is moving fast, and updates to the core libs and tools are pushed regularly.
Fortunately, the Angular team provides tools to help you follow through the updates:
-
npm run ng updateallows you to update your app and its dependencies -
The Angular update website guides you through Angular changes and migrations, providing step by step guides from one version to another.