On-Premises Code Management via Cloud Gateway

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

There is a challenge in managing and integrating cloud SaaS solutions with on-premises server systems for source code management, particularly in maintaining control over code and documentation while utilizing cloud-based services.

Innovation Solution

The integration of on-premises server systems with cloud server systems is achieved through a networked environment where an on-premises server provides a document management service, including a source code management system like Git, and a cloud server system offers SaaS solutions, with proxy applications ensuring secure communication and user authentication, allowing for seamless access and management of code repositories.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Ease of operation

If cloud SaaS solutions are integrated with on-premises server systems for source code management, then access and management of code repositories becomes seamless and efficient, but control and security over code may be compromised

Engineering Contradiction:
Improveaccess and management of code repositoriesVSAvoidcontrol and security over code
Core Design Contradiction:
Ease of operationVSReliability

Solution Approach 1:

The patent implements a gateway component that acts as an intermediary between the cloud SaaS platform and the on-premises source code management system. This gateway receives requests from the cloud platform, translates them into appropriate commands for the local system, and returns results while maintaining security boundaries. The gateway enables seamless access to code repositories through the cloud interface while preserving control and security through the local system architecture.

Inventive Principle:
Principle #24Intermediary (Mediator)

2Reliability

If on-premises server systems are used to maintain control over code, then security and control are ensured, but integration with cloud-based services becomes complex

Engineering Contradiction:
Improvecontrol and security over codeVSAvoidintegration with cloud-based services
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The system is segmented into distinct functional components: the on-premises source code management system that maintains security and control, the cloud SaaS platform that provides user interface and collaboration features, and the gateway that handles communication between them. This segmentation allows each component to operate independently with clearly defined interfaces, simplifying integration while maintaining security requirements.

Inventive Principle:
Principle #1Segmentation

3Productivity

If cloud-based services are leveraged for workflow management and code review, then productivity and collaboration are improved, but dependency on external systems increases

Engineering Contradiction:
Improveworkflow management and code reviewVSAvoiddependency on external systems
Core Design Contradiction:
ProductivityVSAdaptability or versatility

Solution Approach 1:

The gateway serves as a mediator that enables the on-premises system to leverage cloud-based workflow management and code review capabilities while maintaining the option to operate independently. The gateway translates cloud platform commands into local system operations, allowing the organization to use cloud services when needed while retaining autonomy and adaptability to external system changes or outages.

Inventive Principle:
Principle #24Intermediary (Mediator)

Data Source

PatentUS20210303297A1Systems and methods for remote code review
Publication Date: 2021.09.30 ATLASSIAN PTY LTD
  • US20210303297A1 patent drawing
  • US20210303297A1 patent drawing
  • US20210303297A1 patent drawing

AI summary

Described herein is a computer implemented method including a server system communicating identifier(s) identifying to a document management service of a second server system a portion of software code or other document parts. The identified code or document parts are communicated to a client system. A variation of or addition to the code or document is received from the client system and the server system communicates to the document management service the variation and the identifier(s).