When I first wrote about the differences between services and factories in Angular, the bottom line was that the difference is semantic and so you should just pick one and stick with it.
Back then I made the point that, personally, I find factories require less boilerplate code and so they are often my choice.
Since then, a use case for using services has become more common, and that’s when using ES6/ES2015 classes.
When making use of classes, services are the right choice.
That’s because classes map naturally to an Angular service, let’s see how.
Take a look at this non-ES6
1 2 3 4 5 6
Converting this to an ES6 class would look like this:
1 2 3 4 5 6 7 8
The registration line would then be changed to this:
The behavior for all existing code that injects
UsersStore will remain the same, this is a seamless transition.
An important note, though, is the way injection is now performed.
$http is now provided to the class’s
In order to be able to access the injected service later, for example in the
getAll method, we have to save it as a member.
Then, the code in the converted
getAll function should make sure to reference it as
The extra typing around a constructor might put off some people, but looking at the bright side I find it helps making it more painful to write uber controllers and services that take on too much responsibility :)
Subscribe below to learn more about modern Angular and using Angular with ES6.
“Maintaining AngularJS feels like Cobol 🤷…”
You want to do AngularJS the right way.
Yet every blog post you see makes it look like your codebase is obsolete. Components? Lifecycle hooks? Controllers are dead?
It would be great to work on a modern codebase again, but who has weeks for a rewrite?
Well, you can get your app back in shape, without pushing back all your deadlines! Imagine, upgrading smoothly along your regular tasks, no longer deep in legacy.
Subscribe and get my free email course with steps for upgrading your AngularJS app to the latest 1.6 safely and without a rewrite.