API Service Platform Automating VM and Load Balancer Provisioning

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Current web service platforms face challenges in configuring and managing Application Programming Interfaces (APIs) as a service, particularly in scaling and throttling, which are essential for efficient resource management and security, but are often lacking in existing solutions.

Innovation Solution

The implementation of a multi-customer web services platform that includes a service manager to provision virtual machine instances, configure load balancers, and manage DNS information, along with features for throttling and scaling, to streamline the process of setting up and managing APIs as a service.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Ease of operation

If web service platforms manually configure and manage APIs, then flexibility and control are improved, but configuration complexity and management effort increase significantly

Engineering Contradiction:
ImproveAPI configuration effortVSAvoidConfiguration complexity
Core Design Contradiction:
Ease of operationVSDevice complexity

Solution Approach 1:

The system enables self-service through automated API provisioning where the platform automatically configures and manages APIs without requiring manual intervention. The service manager autonomously handles virtual machine instance provisioning, load balancer configuration, and DNS setup, reducing both configuration effort and complexity simultaneously.

Inventive Principle:
Principle #25Self-service

Solution Approach 2:

The system performs preliminary action by pre-configuring API management templates and policies that include throttling and scaling settings. These pre-configured templates are automatically applied when new APIs are provisioned, eliminating the need for manual configuration of each API component and reducing overall configuration complexity.

Inventive Principle:
Principle #10Preliminary action

2Productivity

If web service platforms lack integrated throttling and scaling features, then system simplicity is maintained, but resource management efficiency and security deteriorate

Engineering Contradiction:
ImproveResource management efficiencyVSAvoidSystem complexity
Core Design Contradiction:
ProductivityVSDevice complexity

Solution Approach 1:

The system merges throttling, scaling, authentication, and API management features into a single integrated service manager. This consolidation improves resource management efficiency by enabling coordinated control of multiple functions while managing system complexity through unified architecture rather than separate independent components.

Inventive Principle:
Principle #5Merging (Combining)

Solution Approach 2:

The service manager is designed with multi-functionality to handle diverse API management tasks including provisioning, throttling, scaling, and authentication within a single platform. This universal approach improves resource management efficiency by providing comprehensive control while avoiding the complexity of multiple separate systems.

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

3Loss of time

If web service platforms lack automated provisioning capabilities, then system simplicity is preserved, but deployment time and manual effort increase

Engineering Contradiction:
ImproveAPI deployment timeVSAvoidProvisioning automation
Core Design Contradiction:
Loss of timeVSExtent of automation

Solution Approach 1:

The system implements self-service automated provisioning where the service manager automatically creates and configures virtual machine instances, load balancers, and DNS records without manual intervention. This automation dramatically reduces API deployment time while establishing a robust automated infrastructure.

Inventive Principle:
Principle #25Self-service

Solution Approach 2:

The system performs preliminary action by pre-defining provisioning templates and automation workflows that prepare all necessary configuration parameters and resource allocations in advance. When an API needs to be deployed, the pre-prepared automation routines execute immediately, minimizing deployment time without requiring complex real-time decision-making systems.

Inventive Principle:
Principle #10Preliminary action

Data Source

PatentUS11507439B1Application programming interface as a service
Publication Date: 2022.11.22 AMAZON TECH INC
  • US11507439B1 patent drawing
  • US11507439B1 patent drawing
  • US11507439B1 patent drawing

AI summary

An application programming interface (API) as a service is disclosed. In embodiments, a client provides code to be executed along with a configuration file for that code. Based on that, virtual machine(s) and load balancer(s) may be selected, a domain name service configured, and throttling and scaling configured. Through this, an API as a service may be provided on behalf of a client with minimal configuration required by the client or an administrator of a web service platform that provides the API as a service.