API Object Pool for Serverless Application Development

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Current application development processes are costly and time-consuming, especially for multi-platform enterprise applications, due to static logic flows and limited customization, requiring extensive development, testing, and server deployment efforts, and fail to effectively integrate different applications without significant technical expertise.

Innovation Solution

A computational abstraction layer formed of 'Parjects' generated from worldwide APIs, allowing developers to create applications without requiring their own servers, using a no-code Integrated Development Environment (IDE) that represents any computational IP-connected capability as an object, enabling easy customization and orchestration of diverse capabilities.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Productivity

If traditional application development approaches are used with static logic flows and separate server deployment, then application functionality can be achieved, but development cost and time increase significantly

Engineering Contradiction:
Improveapplication development speedVSAvoiddevelopment complexity
Core Design Contradiction:
ProductivityVSDevice complexity

Solution Approach 1:

The patent introduces an intermediary layer (the platform with pre-built API integrations and object library) that mediates between developers and multiple application APIs. This intermediary provides standardized connection mechanisms and pre-configured integration templates, eliminating the need for developers to manually establish complex connections between different applications and reducing both development time and complexity.

Inventive Principle:
Principle #24Intermediary (Mediator)

Solution Approach 2:

The patent segments the complex application development process into modular components: reusable API objects, pre-configured integration templates, and standardized connection protocols. By breaking down the monolithic development process into these manageable segments, developers can assemble applications from predefined building blocks rather than coding everything from scratch, significantly reducing development effort.

Inventive Principle:
Principle #1Segmentation

2Adaptability or versatility

If multiple application integrations are implemented with custom development, then application capability increases, but integration effort and maintenance cost increase

Engineering Contradiction:
Improveapplication integration capabilityVSAvoidintegration effort
Core Design Contradiction:
Adaptability or versatilityVSEase of manufacture

Solution Approach 1:

The patent creates a universal integration platform that provides multi-functional capabilities for connecting with multiple different applications through standardized mechanisms. The platform offers a common object library and integration templates that can be applied across different application types, allowing the same integration approach to work universally with various APIs rather than requiring custom development for each integration scenario.

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

Solution Approach 2:

The patent enables easy integration by allowing parameter-based configuration rather than code-based customization. Integration parameters such as API endpoints, authentication credentials, and data mapping rules can be changed through configuration files or interface settings, enabling rapid adaptation to different applications without modifying the underlying integration logic or requiring developer expertise in each specific API protocol.

Inventive Principle:
Principle #35Parameter changes

3Ease of operation

If application developers deploy applications with their own servers, then application control is maintained, but infrastructure management burden increases

Engineering Contradiction:
Improveapplication deployment simplicityVSAvoidinfrastructure complexity
Core Design Contradiction:
Ease of operationVSDevice complexity

Solution Approach 1:

The patent extracts the server infrastructure management burden from the application deployment process and places it in the platform layer. The platform handles server provisioning, maintenance, security updates, and scalability management independently, allowing developers to focus solely on application logic and user interface development. This separation extracts the complex infrastructure tasks from the developer's responsibility while maintaining full application control through the platform's API.

Inventive Principle:
Principle #2Taking out (Extraction)

Data Source

PatentUS10896035B1Methods of converting APIs into objects and uses thereof
Publication Date: 2021.01.19 ABDULHAYOGLU MELIH
  • US10896035B1 patent drawing
  • US10896035B1 patent drawing
  • US10896035B1 patent drawing

AI summary

There is provided a method of converting APIs into objects and allowing developers to create applications using these objects and deploying them without requiring their own servers. An application is created over an integrated development environment and run on a cloud based environment with the application using at least one object as a capability function. The application is in communication with a computing abstract layer which comprises an object pool with a plurality of objects and an identifier associated with each object. An object dispatcher checks the use of the object in the application and directs the request to a worldwide API or an agent application running on devices. Responses are returned to the applications.