people think:
“If I can see a service in the marketplace, then it must be ready to use.”
That is not true.
The missing link here is understanding the difference between
Entitlements and Service Instances.
Entitlement simply means permission.
When an admin assigns an entitlement, SAP is saying:
“This subaccount is allowed to use this service, with this plan, up to this limit.”
Nothing is created at this point.
No service is running.
No resource is consumed.
It is only permission.
A service instance is the real thing.
This is when:
-
a database is actually created
-
an integration runtime is actually provisioned
-
a service starts consuming resources
Service instances are created inside spaces, usually by developers.
This is where:
-
quota is consumed
-
limits are reached
-
costs can start adding up
Think of it like this:
-
Entitlement → permission to enter a room
-
Service Instance → actually sitting inside the room and using it
Admins control the permission.
Developers usually consume the instance.
Admins are responsible for:
-
assigning entitlements
-
deciding plans and quotas
-
controlling which subaccount can use what
Developers are responsible for:
-
creating service instances
-
binding them to applications
-
using the service
Comments
Post a Comment