BaaS Custom Code Source Control Isolation

Resolve Bottlenecks,
Find Innovative SolutionsGenerate Solutions

Solution Overview

Problem

Existing Backend-as-a-Service (BaaS) solutions do not support source control for custom code without exposing host code, limiting developers' ability to manage their custom code while maintaining control over the underlying host code.

Innovation Solution

Implementing a system that provides selective source control for custom code within a BaaS module, allowing developers to manage and modify custom code without accessing or controlling the host code, by using an interface and source control logic to isolate and manage custom code within a runtime environment.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Ease of operation

If source control is provided for custom code in BaaS solutions, then developers can manage and version their custom code, but host code is also exposed which compromises security and control for the BaaS provider

Engineering Contradiction:

Improvesource control managementVSAvoidhost code exposure

Core Design Contradiction:

Ease of operationVSObject-affected harmful factors

Solution Approach 1:

The system segments source control access by creating separate source control repositories: one for custom code (accessible to developers) and one for host code (isolated and controlled by BaaS provider). This segmentation allows developers to have source control for their custom code without exposing the underlying host code that implements the BaaS functionality.

Inventive Principle:

Principle #1Segmentation

Solution Approach 2:

The invention extracts custom code from the host code environment and places it in a separate, isolated source control system. Custom code is loaded into the runtime as compiled or interpreted binaries rather than source code, effectively taking out the source control capability from the host code while preserving it for custom code.

Inventive Principle:

Principle #2Taking out (Extraction)

2Adaptability or versatility

If BaaS solutions allow custom code execution, then developers can extend functionality, but maintaining separate source control for custom code increases system complexity

Engineering Contradiction:

Improvecustom code executionVSAvoidsource control management

Core Design Contradiction:

Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The invention introduces an intermediary layer (the BaaS runtime environment) that loads custom code as compiled binaries or interpreted code rather than source code. This intermediary approach allows custom code execution and version control without requiring the complexity of full source control integration, as the runtime handles loading and management of custom code versions.

Inventive Principle:

Principle #24Intermediary (Mediator)

Data Source

PatentUS11656865B2Enabling access to backend code that defines custom backend feature(s) without enabling access to host code that hosts the backend code

Publication Date: 2023.05.23 MICROSOFT TECHNOLOGY LICENSING LLC

AI summary

Techniques are described herein that are capable of providing source control of custom code in a backend-as-a-service (BaaS) module. For instance, the custom code may be automatically loaded dynamically (e.g., on-demand) in a runtime that is hosted by the BaaS module while the runtime is running to provide custom backend features that are defined by the custom code to an application in response to receipt of a request from the application. Source control of the custom code may be provided without providing source control of host code that defines the runtime.