Micro-Service Gateway for Low-Latency HTTP Request Processing

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing HTTP processing methods are not well-suited for micro-services architecture, making it difficult to implement low-latency and real-time services due to the monolithic nature of current HTTP application servers.

Innovation Solution

Embedding blocks of program code/data into the HTTP request header to seamlessly integrate micro-services transactions into the HTTP protocol, allowing specialized micro-services to process inputs and generate responses efficiently, utilizing specialized hardware and software configurations.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Productivity

If monolithic HTTP application servers are used to process requests, then data processing capacity is sufficient, but service latency increases and real-time processing becomes difficult

Engineering Contradiction:
Improvedata processing capacityVSAvoidservice latency
Core Design Contradiction:
ProductivityVSLoss of time

Solution Approach 1:

The patent segments the monolithic HTTP application server into multiple specialized micro-services, where each micro-service handles specific processing tasks. This segmentation allows parallel processing of different request components, reducing overall service latency while maintaining sufficient data processing capacity through distributed architecture.

Inventive Principle:
Principle #1Segmentation

2Productivity

If specialized micro-services are introduced for efficient processing, then processing efficiency improves, but system complexity increases

Engineering Contradiction:
Improveprocessing efficiencyVSAvoidsystem complexity
Core Design Contradiction:
ProductivityVSDevice complexity

Solution Approach 1:

The patent implements a universal gateway that handles multiple functions including request routing, protocol translation, and coordination among micro-services. This universal component simplifies the overall system architecture by providing a single entry point and abstraction layer, thereby reducing system complexity despite the presence of multiple specialized micro-services.

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

3Adaptability or versatility

If HTTP protocol is used for micro-services communication, then compatibility is maintained, but transaction integration becomes difficult

Engineering Contradiction:
Improveprotocol compatibilityVSAvoidtransaction integration complexity
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The patent introduces an intermediary gateway that mediates between the HTTP protocol and micro-service transactions. This gateway translates HTTP requests into internal micro-service transactions and manages the integration complexity, allowing micro-services to communicate efficiently while maintaining HTTP protocol compatibility at the boundary.

Inventive Principle:
Principle #24Intermediary (Mediator)

Data Source

PatentUS11240289B2Apparatus and method for low-latency message request/response processing
Publication Date: 2022.02.01 SALESFORCE INC
  • US11240289B2 patent drawing
  • US11240289B2 patent drawing
  • US11240289B2 patent drawing

AI summary

An apparatus and method for low-latency real-time request processing. For example, one implementation comprises a front end and a plurality of micro-services each utilizing a different type of hardware and/or software tailored to perform a specialized type of processing. In one implementation, the front end receives a request message (e.g., an HTTP request) containing program code/data in its header and forwards the request to certain micro-services in accordance with the type of processing required and/or other variables such as load on the micro-services. A central storage may be shared by the front end and the micro-services to exchange data and/or the data may be stored in the intermediate messages passed between the front end and micro-services.