paulononato/backstage
1
0
Fork 0
Code Issues Pull Requests Actions 39 Packages Projects Releases Wiki Activity

Fix typo in 03-services.md

Browse Source 
Signed-off-by: Jonas Müller <sanjom96@gmail.com>
This commit is contained in:
Jonas Müller
2024-05-28 13:28:14 +02:00
committed by GitHub
parent dc865c4f52
commit 73ca211b4b
1 changed files with 1 additions and 1 deletions
Download Patch File Download Diff File Expand all files Collapse all files
docs/backend-system/architecture/03-services.md
+1 -1
View File
@@ -111,7 +111,7 @@ There are only two possible scopes for services, `'plugin'` and `'root'`.
## Root Scoped Services
If a service is defined as a root scoped service, the implementation created by the factory will be shared across all plugins and services. One other differentiating factory for root scoped services is that they are always initialized, regardless of whether any plugins depend on them or not. This makes them suitable for implementing backend-wide concerns that are not specific to any individual plugin.
If a service is defined as a root scoped service, the implementation created by the factory will be shared across all plugins and services. One other differentiating factors for root scoped services is that they are always initialized, regardless of whether any plugins depend on them or not. This makes them suitable for implementing backend-wide concerns that are not specific to any individual plugin.
There is a limitation in the usage of root scoped services, which is that their implementation can only depend on other root scoped services. Plugin scoped services on the other hand can depend on both root and plugin scoped services. Because of this limitation, one of the main reasons to define a root scoped services is to make it possible for other root scoped services to depend on it.