Provisioning multi-tenant, microservice architecture-based integration service in a cloud computing environment

1. A system associated with a cloud computing environment, comprising:

a data storage device containing user identifiers and associated entitlement values for a plurality of tenants of the cloud computing environment, wherein the entitlement values are associated with tenant payments;

a platform resource manager, at an integration service, having access to the cloud computing environment; and

a provisioning application platform, between a user device and the platform resource manager and coupled to the data storage device, to: (i) receive from the user device a user subscribe request for an integration design application associated with an inbuild event publish/subscribe framework, (ii) access the data storage device, and (iii) transmit at least one entitlement value to the platform resource manager to facilitate creation of a plurality of microservices, by the integration service, resulting in implementation of the integration design application for the user,

wherein the platform resource manager is to: (i) create tenant specific resources based on the at least one entitlement value via the inbuild event publish/subscribe framework, wherein the at least one entitlement value is associated with an account storage limit or a Service Level Agreement (“SLA”), (ii) create tenant specific instances, and (iii) bind applications to the resources and instances to create the integration design application.

2. The system of claim 1 , wherein at least one microservice is associated with at least one of: (i) an integration design user interface application, (ii) a monitoring user interface application, (iii) a runtime working node, (iv) an information storage service, and (v) database resources.

3. The system of claim 1 , wherein the provisioning application platform is associated with at least one of: (i) a Software-as-a-Service, and (ii) a Platform-as-a-Service.

4. The system of claim 1 , wherein the provisioning application platform is further to verify that tenant-onboarding is completed successfully.

5. The system of claim 1 , wherein the provisioning application platform accesses entitlement information stored in at least one of: (i) a scope of the provisioning application platform, and (ii) a commercialization component of a cloud computing environment platform.

6. The system of claim 1 , wherein the provisioning application platform further supports a decommissioning process.

7. A non-transitory, computer-readable medium having executable instructions stored therein, the medium comprising:

instructions to receive, at a provisioning application platform from a user device, a user subscribe request for an integration design application associated with an inbuild event publish/subscribe framework, wherein the provisioning application platform is between the user device and a platform resource manager of an integration service;

instructions to access, by the provisioning application platform, a data storage device, coupled to the provisioning application platform, containing user identifiers and associated entitlement values for a plurality of tenants of the cloud computing environment, wherein the entitlement values are associated with tenant payments; and

instructions to transmit at least one entitlement value to the platform resource manager to facilitate creation of a plurality of microservices resulting in implementation of the integration design application for the user,

wherein the platform resource manager is to: (i) create tenant specific resources based on the at least one entitlement value via the inbuild event publish/subscribe framework, wherein the at least one entitlement value is associated with an account storage limit or a Service Level Agreement (“SLA”), (ii) create tenant specific instances, and (iii) bind applications to the resources and instances to create the integration design application.

8. The non-transitory, computer-readable medium of claim 7 , wherein at least one microservice is associated with at least one of: (i) an integration design user interface application, (ii) a monitoring user interface application, (iii) a runtime working node, (iv) an information storage service, and (v) database resources.

9. The non-transitory, computer-readable medium of claim 7 , wherein the provisioning application platform is associated with at least one of: (i) a Software-as-a-Service, and (ii) a Platform-as-a-Service.

10. The non-transitory, computer-readable medium of claim 7 , wherein the provisioning application platform is further to verify that tenant-onboarding is completed successfully.

11. The non-transitory, computer-readable medium of claim 7 , wherein the provisioning application platform accesses entitlement information stored in at least one of: (i) a scope of the provisioning application platform, and (ii) a commercialization component of a cloud computing environment platform.

12. The non-transitory, computer-readable medium of claim 7 , wherein the provisioning application platform further supports a decommissioning process.

13. A computer-implemented method associated with a cloud computing environment, comprising:

receiving, at a provisioning application platform from a user device, a user subscribe request for an integration design application associated with an inbuild event publish/subscribe framework, wherein the provisioning application platform is between the user device and a platform resource manager of an integration service;

accessing, by the provisioning application platform, a data storage device, coupled to the provisioning application platform, containing user identifiers and associated entitlement values for a plurality of tenants of the cloud computing environment, wherein the entitlement values are associated with tenant payments; and

transmitting at least one entitlement value to a platform resource manager to facilitate creation of a plurality of microservices resulting in implementation of the integration design application for the user,

wherein the platform resource manager is to: (i) create tenant specific resources based on the at least one entitlement value via the inbuild event publish/subscribe framework, wherein the at least one entitlement value is associated with an account storage limit or a Service Level Agreement (“SLA”), (ii) create tenant specific instances, and (iii) bind applications to the resources and instances to create the integration design application.

14. The method of claim 13 , wherein at least one microservice is associated with at least one of: (i) an integration design user interface application, (ii) a monitoring user interface application, (iii) a runtime working node, (iv) an information storage service, and (v) database resources.

15. The method of claim 13 , wherein the provisioning application platform is associated with at least one of: (i) a Software-as-a-Service, and (ii) a Platform-as-a-Service.

16. The method of claim 13 , wherein the provisioning application platform is further to verify that tenant-onboarding is completed successfully.

17. The method of claim 13 , wherein the provisioning application platform accesses entitlement information stored in at least one of: (i) a scope of the provisioning application platform, and (ii) a commercialization component of a cloud computing environment platform.

18. The method of claim 13 , wherein the provisioning application platform further supports a decommissioning process.