Runtime Server for Tierless Application Coding

Resolve Bottlenecks,
Find Innovative SolutionsGenerate Solutions

Solution Overview

Problem

The increasing complexity of technology stacks in business application development, particularly in service-oriented architectures, leads to higher costs, longer development times, and the need for specialized resources, making it difficult for enterprises to maintain and update applications efficiently.

Innovation Solution

A system-oriented programming infrastructure that allows for universal programmability across existing servers using event-based instruction sets and run-time servers, enabling interaction with multiple programmable code interfaces and automatic generation of interfacing instructions for seamless communication between different technology layers.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If service-oriented architecture with multiple technologies is used, then application functionality and versatility are improved, but device complexity and development cost increase

Engineering Contradiction:

Improveapplication functionalityVSAvoidtechnology stack complexity

Core Design Contradiction:

Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The patent introduces a runtime server as an intermediary layer between event-based instruction sets and existing servers. The runtime server automatically generates interfacing instructions that translate between different technology interfaces, eliminating the need for developers to manually handle complex interface translations between multiple technologies in the stack.

Inventive Principle:

Principle #24Intermediary (Mediator)

Solution Approach 2:

The runtime server provides universal programmability by supporting multiple programmable code interfaces simultaneously. A single runtime server can interface with various existing servers through different interfaces (SOAP, REST, messaging queues, etc.), making the system adaptable to diverse technologies without requiring separate specialized interfaces for each.

Inventive Principle:

Principle #6Universality (Multi-functionality)

2Adaptability or versatility

If multiple specialized technologies are integrated, then system capability is improved, but loss of time for development and maintenance increases

Engineering Contradiction:

Improvesystem capabilityVSAvoiddevelopment time

Core Design Contradiction:

Adaptability or versatilityVSLoss of time

Solution Approach 1:

The runtime server performs preliminary action by automatically generating interfacing instructions before the application needs to communicate between different technologies. The system pre-compiles and stores these interfacing instructions, so that at runtime, communication between technologies occurs instantly without manual intervention or time-consuming translation processes.

Inventive Principle:

Principle #10Preliminary action

Solution Approach 2:

The runtime server serves itself by automatically generating the necessary interfacing instructions when event-based instruction sets are received. This self-service capability eliminates the need for manual configuration of interfaces between technologies, significantly reducing development time and allowing the system to adapt to new technologies autonomously.

Inventive Principle:

Principle #25Self-service

3Manufacturing precision

If tiered application architecture with specialized building blocks is used, then manufacturing precision and functional separation are improved, but device complexity and coding difficulty increase

Engineering Contradiction:

Improvefunctional separationVSAvoidarchitecture complexity

Core Design Contradiction:

Manufacturing precisionVSDevice complexity

Solution Approach 1:

The patent segments the application into event-based instruction sets that are independent of specific technology tiers. Instead of coding separate building blocks for each tier (presentation, business logic, data), the system uses a single segmented approach where events are processed uniformly across all tiers by the runtime server, eliminating the complexity of tier-specific coding while maintaining functional separation.

Inventive Principle:

Principle #1Segmentation

Solution Approach 2:

The patent inverts the traditional tiered architecture approach by not having each tier coded with specialized building blocks. Instead, a single inverted approach uses event-based instruction sets that are universally processed by the runtime server, reversing the conventional wisdom that each tier needs specialized optimization. This inversion simplifies coding while preserving the benefits of functional separation.

Inventive Principle:

Principle #13The other way round (Inversion)

4Reliability

If technology-specific interfaces are implemented for each server, then reliability of communication is improved, but device complexity and coding effort increase

Engineering Contradiction:

Improvecommunication reliabilityVSAvoidinterface complexity

Core Design Contradiction:

ReliabilityVSDevice complexity

Solution Approach 1:

The runtime server implements universality by supporting multiple programmable code interfaces through a single unified mechanism. Instead of implementing separate specialized interfaces for each server type, the runtime server provides a universal interface that automatically adapts to different technologies, maintaining communication reliability while eliminating the complexity of multiple specialized interfaces.

Inventive Principle:

Principle #6Universality (Multi-functionality)

Data Source

PatentUS10530838B1System oriented programming and implementation infrastructure, system and method

Publication Date: 2020.01.07 YOUPROGRAM SOFTWARE SOLUTIONS INC

AI summary

Described are various embodiments of a system-oriented programming and implementation infrastructure, system and method.