Abstract: Methods, systems, and computer program products are provided that automatically scale an application between private and public cloud computing platforms, while simultaneous enforcing policies ensuring private data is persistently stored on the private cloud computing platform, but not the public cloud computing platform. A traffic manager on the public platform routes traffic to instances of a web app executing on a private platform. A traffic monitor on the private platform monitors performance criteria of the private platform, and reports traffic telemetry to the traffic manager. Based on the traffic telemetry, the traffic manager may instantiate one or more instances of the web app on the public platform to handle traffic. Private data gathered by such instantiated instance(s) is persisted to storage in the private platform, but not in the public platform.

Abstract: Methods, systems, and computer program products are provided that automatically scale an application between private and public cloud computing platforms, while simultaneous enforcing policies ensuring private data is persistently stored on the private cloud computing platform, but not the public cloud computing platform. A traffic manager on the public platform routes traffic to instances of a web app executing on a private platform. A traffic monitor on the private platform monitors performance criteria of the private platform, and reports traffic telemetry to the traffic manager. Based on the traffic telemetry, the traffic manager may instantiate one or more instances of the web app on the public platform to handle traffic. Private data gathered by such instantiated instance(s) is persisted to storage in the private platform, but not in the public platform.

Abstract: Methods, systems, and computer program products are provided that automatically scale an application between private and public cloud computing platforms, while simultaneous enforcing policies ensuring private data is persistently stored on the private cloud computing platform, but not the public cloud computing platform. A traffic manager on the public platform routes traffic to instances of a web app executing on a private platform. A traffic monitor on the private platform monitors performance criteria of the private platform, and reports traffic telemetry to the traffic manager. Based on the traffic telemetry, the traffic manager may instantiate one or more instances of the web app on the public platform to handle traffic. Private data gathered by such instantiated instance(s) is persisted to storage in the private platform, but not in the public platform.

Abstract: Methods, systems, and computer program products are provided that automatically scale an application between private and public cloud computing platforms, while simultaneous enforcing policies ensuring private data is persistently stored on the private cloud computing platform, but not the public cloud computing platform. A traffic manager on the public platform routes traffic to instances of a web app executing on a private platform. A traffic monitor on the private platform monitors performance criteria of the private platform, and reports traffic telemetry to the traffic manager. Based on the traffic telemetry, the traffic manager may instantiate one or more instances of the web app on the public platform to handle traffic. Private data gathered by such instantiated instance(s) is persisted to storage in the private platform, but not in the public platform.

Abstract: User interface integration across multiple clouds is achieved by hosting UI extensions for different services in the same browser window. The UI extensions are initialized by a shell with any necessary security context for the corresponding cloud. The shell provides versioning so that the newest version of the UI is presented to users for all versions of a service. A connector in a local cloud provides translation between APIs across different clouds.

Abstract: User interface integration across multiple clouds is achieved by hosting UI extensions for different services in the same browser window. The UI extensions are initialized by a shell with any necessary security context for the corresponding cloud. The shell provides versioning so that the newest version of the UI is presented to users for all versions of a service. A connector in a local cloud provides translation between APIs across different clouds.

Abstract: Embodiments provide an API that provides metadata about a cloud service's endpoints in response to a single query. This allows a cloud service to advertise each of its endpoints through a common endpoint. The common endpoint may be present in each of a plurality of cloud services, thereby allowing each cloud service automatically discover metadata for other cloud services.

Abstract: Methods, systems, and computer program products are provided that automatically scale an application between private and public cloud computing platforms, while simultaneous enforcing policies ensuring private data is persistently stored on the private cloud computing platform, but not the public cloud computing platform. A traffic manager on the public platform routes traffic to instances of a web app executing on a private platform. A traffic monitor on the private platform monitors performance criteria of the private platform, and reports traffic telemetry to the traffic manager. Based on the traffic telemetry, the traffic manager may instantiate one or more instances of the web app on the public platform to handle traffic. Private data gathered by such instantiated instance(s) is persisted to storage in the private platform, but not in the public platform.

Abstract: User interface integration across multiple clouds is achieved by hosting UI extensions for different services in the same browser window. The UI extensions are initialized by a shell with any necessary security context for the corresponding cloud. The shell provides versioning so that the newest version of the UI is presented to users for all versions of a service. A connector in a local cloud provides translation between APIs across different clouds.

Abstract: Embodiments provide an API that provides metadata about a cloud service's endpoints in response to a single query. This allows a cloud service to advertise each of its endpoints through a common endpoint. The common endpoint may be present in each of a plurality of cloud services, thereby allowing each cloud service automatically discover metadata for other cloud services.

Abstract: Embodiments provide an API that provides metadata about a cloud service's endpoints in response to a single query. This allows a cloud service to advertise each of its endpoints through a common endpoint. The common endpoint may be present in each of a plurality of cloud services, thereby allowing each cloud service automatically discover metadata for other cloud services.

Abstract: User interface integration across multiple clouds is achieved by hosting UI extensions for different services in the same browser window. The UI extensions are initialized by a shell with any necessary security context for the corresponding cloud. The shell provides versioning so that the newest version of the UI is presented to users for all versions of a service. A connector in a local cloud provides translation between APIs across different clouds.

Abstract: User interface integration across multiple clouds is achieved by hosting UI extensions for different services in the same browser window. The UI extensions are initialized by a shell with any necessary security context for the corresponding cloud. The shell provides versioning so that the newest version of the UI is presented to users for all versions of a service. A connector in a local cloud provides translation between APIs across different clouds.

Abstract: An application may be configured with two or more cloud contexts and one or more identity Systems. Using this information, the application has the ability to identify the remote cloud environment that a particular subsystem needs to interact with. The application communicates with the appropriate identity system to retrieve tokens dynamically for targeting that remote cloud.

Abstract: An application may be configured with two or more cloud contexts and one or more identity Systems. Using this information, the application has the ability to identify the remote cloud environment that a particular subsystem needs to interact with. The application communicates with the appropriate identity system to retrieve tokens dynamically for targeting that remote cloud.

Abstract: Embodiments provide an API that provides metadata about a cloud service's endpoints in response to a single query. This allows a cloud service to advertise each of its endpoints through a common endpoint. The common endpoint may be present in each of a plurality of cloud services, thereby allowing each cloud service automatically discover metadata for other cloud services.

Abstract: Embodiments provide a library that allows developers to very quickly build and deploy services or resource providers without having to interpret a complex cloud protocol specification. The SDK implements resource storage, automatically handles resource lifecycle, provides appropriate hooks to plug into external systems, facilitates handling of subscription-wide operations, implements complex flows such as moving of resources, enables appropriate security features, and creates necessary endpoints for the developer's service.

Abstract: User interface integration across multiple clouds is achieved by hosting UI extensions for different services in the same browser window. The UI extensions are initialized by a shell with any necessary security context for the corresponding cloud. The shell provides versioning so that the newest version of the UI is presented to users for all versions of a service. A connector in a local cloud provides translation between APIs across different clouds.

Abstract: A soft switch 134 providing wireless PBX voice services to a local area network (WLAN) is used to extend PBX functionality to the cellular domain. A dual mode remote unit is capable of receiving signals both in the cellular system as well as the WLAN. The cellular system is comprised of a data-bearing path and a voice-bearing path. When the dual mode remote unit is within the WLAN, it communicates both voice over IP (VoIP) signaling as well as session initiation protocol (SIP) control signaling over the WLAN. When the remote unit is outside the WLAN, it communicates voice signaling over the voice-bearing path of the cellular network using a standard cellular voice channel. In parallel, it uses the data-bearing path of the cellular network to transmit SIP control signaling.

Abstract: A soft switch 134 providing wireless PBX voice services to a local area network (WLAN) is used to extend PBX functionality to the cellular domain. A dual mode remote unit is capable of receiving signals both in the cellular system as well as the WLAN. The cellular system is comprised of a data-bearing path and a voice-bearing path. When the dual mode remote unit is within the WLAN, it communicates both voice over IP (VoIP) signaling as well as session initiation protocol (SIP) control signaling over the WLAN. When the remote unit is outside the WLAN, it communicates voice signaling over the voice-bearing path of the cellular network using a standard cellular voice channel. In parallel, it uses the data-bearing path of the cellular network to transmit SIP control signaling.