Custom integration flow step for integration service

1. A system associated with a cloud computing environment having an integration service, comprising:

a design micro service having a User Interface (“UP”) framework and UI components in a domain specific language for an integration developer;

a runtime worker container including an Enterprise Service Bus (“ESB”) framework, ESB components, and integration content; and

a custom flow step development kit that communicates with the runtime worker container, including:

a computer processor, and

a computer memory storing instructions that when executed by the computer processor custom flow step development kit to:

receive, from the integration developer via a browser-based graphical UI, custom flow step build logic associated with a microservice-based integration service,

automatically create, based on the custom flow step build logic, a new UI component and a new runtime ESB component, and

deploy the new UI component and new runtime ESB component to the design micro service and the runtime worker container.

2. The system of claim 1 , wherein the logic is embedded as part of a particular integration scenario and is usable only in an integration flow.

3. The system of claim 1 , wherein a new integration component is embedded into an existing set of components for a tenant, and the new custom flow step is deployed in, and re-usable by, other integration services.

4. The system of claim 1 , wherein the custom flow step development kit supports a custom flow step interface.

5. The system of claim 1 , wherein the integration service is associated with at least one of: (i) a Software-as-a-Service, and (ii) a Platform-as-a-Service.

6. The system of claim 1 , wherein the custom flow step development kit is associated with an application development kit.

7. The system of claim 6 , wherein the application development kit includes a metadata builder, an adapter assembly builder, and a validator.

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

instructions to determine that an integration developer wants to create a new custom flow step component via an adapter development framework;

instructions to receive, from the integration developer, a component name for the custom flow step component via a browser-based development studio;

instructions to receive, from the integration developer, custom code that adheres to an Enterprise Service Bus (“ESB”) to define business logic;

instructions to build the new custom flow step component in accordance with the business logic;

instructions to deploy an ESB component to runtime and a User Interface (“UI”) component to design time in connection with the new custom flow step component, wherein a design micro service has the UI component in a domain specific language for the integration developer;

instructions to receive, by a custom flow step development kit from the integration developer, custom flow step component build logic associated with a microservice-based integration service;

instructions to automatically create, based on the custom flow step component build logic, a new UI component and a new runtime ESB component; and

instructions to deploy the new UI component and the new runtime ESB component to the design micro service and a runtime worker container that includes an ESB framework, ESB components, and integration content.

9. The medium of claim 8 , further comprising:

instructions to display information about the custom flow step component to another integration developer associated with the tenant; and

instructions to arrange for the other integration developer to consume the custom flow step component.

10. The medium of claim 8 , wherein the business logic is embedded as part of a particular integration scenario and is usable only in an integration flow.

11. The medium of claim 8 , wherein a new integration component is embedded into an existing set of components for a tenant, and the new custom flow step is deployed in, and re-usable by, other integration services.

12. The medium of claim 8 , wherein the integration service is associated with at least one of: (i) a Software-as-a-Service, and (ii) a Platform-as-a-Service.

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

determining that an integration developer wants to create a new custom flow step component via an adapter development framework;

receiving, from the integration developer, a component name for the custom flow step component via a browser-based development studio;

receiving, from the integration developer, custom code that adheres to an Enterprise Service Bus (“ESB”) to define business logic;

building the new custom flow step component in accordance with the business logic;

deploying an ESB component to runtime and a User Interface (“UP”) component to design time in connection with the new custom flow step component, wherein a design micro service has the UI component in a domain specific language for the integration developer;

receiving, by a custom flow step development kit from the integration developer, custom flow step component build logic associated with a microservice-based integration service; and

automatically creating, based on the custom flow step component build logic, a new UI component and a new runtime ESB component; and

deploying the new UI component and the new runtime ESB component to the design micro service and a runtime worker container that includes an ESB framework, ESB components, and integration content.

14. The method of claim 13 , wherein the integration developer is associated with a tenant of the cloud computing environment and further comprising:

displaying information about the custom flow step component to another integration developer associated with the tenant; and

arranging for the other integration developer to consume the custom flow step component.

15. The method of claim 13 , wherein the business logic is embedded as part of a particular integration scenario and is usable only in an integration flow.

16. The method of claim 13 , wherein a new integration component is embedded into an existing set of components for a tenant, and the new custom flow step is deployed in, and re-usable by, other integration services.

17. The method of claim 13 , wherein the integration service is associated with at least one of: (i) a Software-as-a-Service, and (ii) a Platform-as-a-Service.

18. The system of claim 1 , further comprising:

an integration system framework middle layer component, to help applications communicate, having a worker node that includes:

worker node integration content to receive inbound calls and provide outbound calls,

worker node user build integration components coupled to the worker node integration content via a worker node ESB framework, and

worker node message discovery to deploy a listener, implement a collector, and execute a write service that publishes information to a messaging system.