Brokering services from partner cloud platforms

1. A computer-implemented method, comprising:

receiving, from a developer and at a Proxy Service Broker on a Hoster Platform as a Service (PaaS), a request for a Service Catalog comprising PaaS services available from a Partner PaaS, wherein the Proxy Service Broker on the Hoster PaaS brokers the PaaS services run by the Partner PaaS by mapping Partner PaaS service creation, and binding service calls to corresponding calls on the Partner PaaS;

initiating creation, by the developer using the Proxy Service Broker, of an instance of a Partner PaaS service selected from the Service Catalog;

generating, by the Proxy Service Broker, a unique service identifier for the instance of the Partner PaaS service to avoid name clashes on the Partner PaaS;

transmitting, using the Proxy Service Broker, a call to a Partner Service Broker on the Partner PaaS to create the instance of the Partner PaaS service executing on the Partner PaaS;

deploying, by the developer, an Application on the Hoster PaaS to consume the instance of the Partner PaaS service;

binding, by the developer, the Application deployed on the Hoster PaaS to the instance of the Partner PaaS service executing on the Partner PaaS; and

directly consuming the Partner PaaS service executing on the Partner PaaS and bound to the Application deployed on the Hoster PaaS by using Hoster PaaS consumer credentials and without requiring Partner PaaS consumer credentials.

2. The computer-implemented method of claim 1 , wherein the Service Catalog of PaaS services is stored on and returned by the Proxy Service Broker.

3. The computer-implemented method of claim 1 , wherein the Proxy Service Broker is associated with a Developer Space associated with the Hoster PaaS.

4. The computer-implemented method of claim 1 , comprising transmitting, using the Proxy Service Broker, a call to the Partner Service Broker on the Partner PaaS to create a service key for the created instance of the Partner PaaS service.

5. The computer-implemented method of claim 4 , wherein a single service user is used to transmit the call to create the instance of the Partner PaaS service and to create the service key for the created instance of the Partner PaaS service.

6. The computer-implemented method of claim 4 , wherein the calls to the Partner PaaS from the Proxy Service Broker are Representational State Transfer (REST) calls.

7. A non-transitory, computer-readable medium storing one or more instructions executable by a computer system to perform operations comprising:

receiving, from a developer and at a Proxy Service Broker on a Hoster Platform as a Service (PaaS), a request for a Service Catalog comprising PaaS services available from a Partner PaaS, wherein the Proxy Service Broker on the Hoster PaaS brokers the PaaS services run by the Partner PaaS by mapping Partner PaaS service creation, and binding service calls to corresponding calls on the Partner PaaS;

initiating creation, by the developer using the Proxy Service Broker, of an instance of a Partner PaaS service selected from the Service Catalog;

generating, by the Proxy Service Broker, a unique service identifier for the instance of the Partner PaaS service to avoid name clashes on the Partner PaaS;

transmitting, using the Proxy Service Broker, a call to a Partner Service Broker on the Partner PaaS to create the instance of the Partner PaaS service executing on the Partner PaaS;

deploying, by the developer, an Application on the Hoster PaaS to consume the instance of the Partner PaaS service;

binding, by the developer, the Application deployed on the Hoster PaaS to the instance of the Partner PaaS service executing on the Partner PaaS; and

directly consuming the Partner PaaS service executing on the Partner PaaS and bound to the Application deployed on the Hoster PaaS by using Hoster PaaS consumer credentials and without requiring Partner PaaS consumer credentials.

8. The non-transitory, computer-readable medium of claim 7 , wherein the Service Catalog of PaaS services is stored on and returned by the Proxy Service Broker.

9. The non-transitory, computer-readable medium of claim 7 , wherein the Proxy Service Broker is associated with a Developer Space associated with the Hoster PaaS.

10. The non-transitory, computer-readable medium of claim 7 , further comprising one or more instructions executable to transmit, using the Proxy Service Broker, a call to the Partner Service Broker on the Partner PaaS to create a service key for the created instance of the Partner PaaS service.

11. The non-transitory, computer-readable medium of claim 10 , wherein a single service user is used to transmit the call to create the instance of the Partner PaaS service and to create the service key for the created instance of the Partner PaaS service.

12. The non-transitory, computer-readable medium of claim 10 , wherein the calls to the Partner PaaS from the Proxy Service Broker are Representational State Transfer (REST) calls.

13. A computer-implemented system, comprising:

a computer memory; and

a hardware processor interoperably coupled with the computer memory and configured to perform operations comprising:

receiving, from a developer and at a Proxy Service Broker on a Hoster Platform as a Service (PaaS), a request for a Service Catalog comprising PaaS services available from a Partner PaaS, wherein the Proxy Service Broker on the Hoster PaaS brokers the PaaS services run by the Partner PaaS by mapping Partner PaaS service creation, and binding service calls to corresponding calls on the Partner PaaS;

initiating creation, by the developer using the Proxy Service Broker, of an instance of a Partner PaaS service selected from the Service Catalog;

generating, by the Proxy Service Broker, a unique service identifier for the instance of the Partner PaaS service to avoid name clashes on the Partner PaaS;

transmitting, using the Proxy Service Broker, a call to a Partner Service Broker on the Partner PaaS to create the instance of the Partner PaaS service executing on the Partner PaaS;

deploying, by the developer, an Application on the Hoster PaaS to consume the instance of the Partner PaaS service;

binding, by the developer, the Application deployed on the Hoster PaaS to the instance of the Partner PaaS service executing on the Partner PaaS; and

directly consuming the Partner PaaS service executing on the Partner PaaS and bound to the Application deployed on the Hoster PaaS by using Hoster PaaS consumer credentials and without requiring Partner PaaS consumer credentials.

14. The computer-implemented system of claim 13 , wherein the Service Catalog of PaaS services is stored on and returned by the Proxy Service Broker.

15. The computer-implemented system of claim 13 , wherein the Proxy Service Broker is associated with a Developer Space associated with the Hoster PaaS.

16. The computer-implemented system of claim 13 , further configured to transmit, using the Proxy Service Broker, a call to the Partner Service Broker on the Partner PaaS to create a service key for the created instance of the Partner PaaS service.

17. The computer-implemented system of claim 16 , wherein:

a single service user is used to transmit the call to create the instance of the Partner PaaS service and to create the service key for the created instance of the Partner PaaS service; and

the calls to the Partner PaaS from the Proxy Service Broker are Representational State Transfer (REST) calls.