---
title: "Comment by Egi Mata on \"Angular Standalone Components\" | Hashnode"
description: "Great article!! Comforting and well structured, but I am a bit sceptic on going all-in for standalone components/services. Is it really a good choice if I start"
url: "https://hashnode.com/posts/angular-standalone-components/6433a28347aba44dec0bf628/comment/6435b8736699be6a40d4e8cf"
---

[Discussion](https://hashnode.com/posts/angular-standalone-components/6433a28347aba44dec0bf628)

Comment [Angular Standalone Components](https://hashnode.com/posts/angular-standalone-components/6433a28347aba44dec0bf628)

[Egi Mata](https://hashnode.com/@egimata)

[Apr 11, 2023](https://hashnode.com/posts/angular-standalone-components/6433a28347aba44dec0bf628/comment/6435b8736699be6a40d4e8cf)

Great article!! Comforting and well structured, but I am a bit sceptic on going all-in for standalone components/services. Is it really a good choice if I start doing it?

I am working with a lot of modules. And I don't know how will I deal with dependency injection of services.

[Mihai Oltean](https://hashnode.com/@ltemihai)

[Apr 12, 2023](https://hashnode.com/posts/angular-standalone-components/6433a28347aba44dec0bf628/comment/6435b8736699be6a40d4e8cf#reply-643663af8c876776a479a31d)

Thank you for the feedback! 🙌🏻

It depends in your case. Do you provide services at root level / module level / component level?

In most of the cases you would want to provide the services at root level.

This way you will be able to use the service in the component just by declaring it in the constructor.

I recommend the following articles for a better decision:

Dependency injection and injectors hierarchy chapter of this article [angular.io/guide/standalone-components](https://angular.io/guide/standalone-components)

and [angular.io/guide/providers](https://angular.io/guide/providers)

Based on the last one you can make a great assessment where would you need to inject the provide the services.

I hope it helps you!