SaaS Extension Points for Third-Party Script Execution
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current SAAS platforms face challenges in handling high volumes of requests during peak events, leading to latency and low availability for third-party applications, especially for small-scale developers.
Innovation Solution
The implementation of extension points within the SAAS platform allows third-party applications to integrate seamlessly by executing scripts directly on the SAAS platform, reducing the need for API calls and alleviating infrastructure capacity issues.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If third-party applications use API calls to run custom functionality outside the SAAS platform, then application flexibility and customization are improved, but latency increases and infrastructure capacity is exceeded during peak events
Solution Approach 1:
The patent merges third-party application execution into the SAAS platform's infrastructure by containerizing applications and running them within the platform's compute environment. This eliminates external API calls and reduces latency while maintaining application flexibility through isolated container execution.
Solution Approach 2:
The patent introduces a container runtime environment as an intermediary layer between the SAAS platform and third-party applications. This mediator enables applications to run directly within the platform infrastructure, reducing communication overhead and latency while preserving application independence through container isolation.
2Adaptability or versatility
If third-party applications run on external infrastructure, then application independence is maintained, but availability decreases during high volume events
Solution Approach 1:
The patent combines third-party applications with the SAAS platform infrastructure through containerization, allowing applications to leverage the platform's scalable resources during peak events. This merging maintains application independence through container isolation while improving availability through shared infrastructure resilience.
Solution Approach 2:
The patent creates a universal container execution environment that can host multiple third-party applications simultaneously on the SAAS platform infrastructure. This multi-functional approach allows the platform to dynamically allocate resources to maintain application availability during high-volume events while preserving application independence.
3Productivity
If applications are integrated into the SAAS platform through extension points, then workflow execution speed is improved, but platform complexity increases
Solution Approach 1:
The patent segments the platform architecture into distinct layers: a standardized extension point interface layer and a containerized application execution layer. This segmentation allows fast workflow execution through direct extension point integration while managing complexity by isolating application-specific logic in separate containers.
Solution Approach 2:
The patent introduces a container runtime intermediary that manages the integration between extension points and third-party applications. This mediator handles the complexity of application lifecycle management, resource allocation, and isolation, allowing fast workflow execution through extension points while containing platform complexity within the runtime layer.
Data Source
Figure 1
Figure 2A
Figure 2B
AI summary
The provided systems and methods attempt to address possible issues with the use of third party applications with software as a service (SAAS) platforms, namely that lack of performance of third party app hosting infrastructure running the third party applications can affect multiple clients on the SAAS platform. In order to least mitigate this, third party app providers can create and upload their scripts to the SAAS platform for execution on the SAAS platform. The scripts must conform with extension points within SAAS functionality that are predefined. During execution, when the extension point is reached, the script is run on the SAAS platform instead of making an API call to the application on the third party app hosting infrastructure.