what is the diffrences between services and providers? both have @injectable and seems to have the same function (to be injected in something). I am from angular background so I kind a confused (or not)?
A provider is something that can be injected (could be a class, or an object, or even a number). When a class is decorated with @Injectable, we know that it's a provider and can be injected and used as a dependancy. It could be a service, or a helper class etc.. A service is used to handle business logic, to keep your application clean and seperated. So instead of putting all your logic in your controller for example, you create a service that takes care of the business logic to keep your code clean and seperared. It's a good idea to decorate a service with @Injectable (marking that specific service as a provider) because that way, we can take advantage of dependancy injection to use it in our application. In this example, we can see that the service is a provider. But a provider doesn't have to be a service. I hope it made things clearer !
![NestJs - Modules [04]](http://i.ytimg.com/vi/eN8ok5yQOTc/mqdefault.jpg)
![NestJs - Modules [04]](/img/tr.png)
Excellent explanation. Keep going. 👌
Very good explanation, may God do good to you!
Thanks! God bless you
great explanation.❤
very well explained!!😀
Greate explanation, take love from heart
Thanks !
thank bro, I really needed this 🤗
You're welcome :)
Great keep going champ ❤
Thank you !
keep it up bro ✌
Thank you !
what is the diffrences between services and providers? both have @injectable and seems to have the same function (to be injected in something). I am from angular background so I kind a confused (or not)?
A provider is something that can be injected (could be a class, or an object, or even a number). When a class is decorated with @Injectable, we know that it's a provider and can be injected and used as a dependancy. It could be a service, or a helper class etc..
A service is used to handle business logic, to keep your application clean and seperated. So instead of putting all your logic in your controller for example, you create a service that takes care of the business logic to keep your code clean and seperared. It's a good idea to decorate a service with @Injectable (marking that specific service as a provider) because that way, we can take advantage of dependancy injection to use it in our application.
In this example, we can see that the service is a provider. But a provider doesn't have to be a service.
I hope it made things clearer !
@@Computerix Greate explanation,