Synchronous Side-by-Side Extensibility via Extension Hub Gateway

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

In multi-tenant cloud computing environments, providing consistent extensibility capabilities across different cloud applications developed on various technology stacks is challenging due to the need for manual, expert-driven processes that are time-consuming and prone to errors, as they require understanding multiple programming tools and technologies.

Innovation Solution

A system architecture that supports synchronous extensibility through an extension hub gateway and orchestrator, allowing customers to define and execute custom logic within the control flow of cloud applications, decoupling the lifecycle of extended code and core logic, and ensuring idempotent extension point implementations for reliable communication.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If manual expert-driven processes are used to implement extensions across multiple cloud applications, then extensibility can be achieved, but the process becomes time-consuming and error-prone

Engineering Contradiction:
Improveextensibility capabilityVSAvoidimplementation time
Core Design Contradiction:
Adaptability or versatilityVSLoss of time

Solution Approach 1:

The patent introduces an extension hub as an intermediary component that mediates between cloud applications and extension implementations. The extension hub provides a standardized interface and automation framework, eliminating the need for manual expert intervention in each extension implementation. This mediator orchestrates the extension lifecycle, manages dependencies, and ensures consistent deployment across multiple cloud applications, thereby reducing implementation time while maintaining extensibility capabilities.

Inventive Principle:
Principle #24Intermediary (Mediator)

2Adaptability or versatility

If manual expert-driven processes are used to implement extensions across multiple cloud applications, then extensibility can be achieved, but the process becomes prone to errors

Engineering Contradiction:
Improveextensibility capabilityVSAvoiderror rate
Core Design Contradiction:
Adaptability or versatilityVSReliability

Solution Approach 1:

The extension hub acts as a reliable intermediary that enforces standardized processes and validation rules. It automatically manages extension deployment, dependency resolution, and lifecycle events, eliminating manual errors. The system provides automated testing, version control, and rollback capabilities, ensuring reliable and consistent extension implementations across multiple cloud applications without human intervention errors.

Inventive Principle:
Principle #24Intermediary (Mediator)

3Adaptability or versatility

If extensions are implemented across different technology stacks, then multi-application extensibility is achieved, but consistency and integration become challenging

Engineering Contradiction:
Improvemulti-application extensibilityVSAvoidintegration complexity
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The patent implements a universal extension hub that provides a single, technology-agnostic interface for extending multiple cloud applications across different technology stacks. The extension hub translates and orchestrates extension logic uniformly, regardless of the underlying application technology. This universal approach allows the same extension mechanism to work across diverse platforms, reducing integration complexity while maintaining multi-application extensibility.

Inventive Principle:
Principle #6Universality (Multi-functionality)

Solution Approach 2:

The extension hub serves as a mediating layer between diverse cloud applications and extension implementations. It handles technology-specific adaptations internally while presenting a consistent interface to users. The hub manages communication protocols, data formats, and integration patterns across different technology stacks, thereby simplifying the overall integration complexity while enabling broad multi-application extensibility.

Inventive Principle:
Principle #24Intermediary (Mediator)

4Ease of manufacture

If cloud application lifecycle is controlled by vendors, then application maintenance is simplified, but customer extensions may be impacted during upgrades

Engineering Contradiction:
Improveapplication maintenanceVSAvoidextension compatibility
Core Design Contradiction:
Ease of manufactureVSReliability

Solution Approach 1:

The patent segments the system into distinct components: the cloud application core (vendor-controlled) and the extension hub (customer-controlled). This segmentation allows independent lifecycle management of each component. The extension hub maintains version compatibility information and manages extension deployments separately from the core application updates. When the vendor releases a new application version, the extension hub can independently assess compatibility, manage transitions, and ensure extensions continue to function, thereby maintaining extension compatibility while preserving vendor-controlled application maintenance.

Inventive Principle:
Principle #1Segmentation

Data Source

PatentUS11048480B1Synchronous side-by-side extensibility
Publication Date: 2021.06.29 SAP SE
  • US11048480B1 patent drawing
  • US11048480B1 patent drawing
  • US11048480B1 patent drawing

AI summary

A system and method providing a single entry point for implementing software extensions across multiple different software applications. In one embodiment, the method may include retrieving an indication of an extension point offered by a cloud application, the extension point being defined by a signature including a name and one or more parameters; generating one or more extension point implementations of the extension point by configuring custom code that fulfills the signature of the extension point; and sending, to the cloud application, an indication the extension point is active for requesting an execution of the one or more extension point implementations to be executed apart from the cloud application.