API Gateway Event Synchronization Across Cloud Data Centers

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing API Gateway solutions face challenges in achieving real-time synchronization across multiple data centers and lack event-based communication for asynchronous operations, particularly in cloud storage environments.

Innovation Solution

Implementing an event-based communication sequence through a traffic manager module that receives messages from an all-in-one module, configures load throttling using cloud storage data, and synchronizes with a key manager and API gateway to achieve real-time synchronization.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If NFS storage is used for data availability across multiple API Gateway instances, then data availability is improved, but real-time synchronization between data centers deteriorates

Engineering Contradiction:
Improvedata availabilityVSAvoidsynchronization speed
Core Design Contradiction:
ReliabilityVSSpeed

Solution Approach 1:

The patent introduces an event message intermediary system that mediates between API Gateway instances and cloud storage. Event messages are published to a subscription-based event system that distributes synchronization notifications across data centers, enabling real-time sync without direct NFS dependencies between distant locations

Inventive Principle:
Principle #24Intermediary (Mediator)

Solution Approach 2:

The system segments the synchronization function into independent event publishers and subscribers. Each API Gateway instance independently publishes events to cloud storage and subscribes to relevant event streams, allowing decentralized real-time synchronization that maintains data availability while achieving cross-datacenter speed

Inventive Principle:
Principle #1Segmentation

2Speed

If cloud storage is used for real-time synchronization, then synchronization speed is improved, but functionality complexity increases

Engineering Contradiction:
Improvesynchronization speedVSAvoidsystem complexity
Core Design Contradiction:
SpeedVSDevice complexity

Solution Approach 1:

The patent implements a universal event message system that handles multiple functions through a single cloud storage interface: configuration retrieval, real-time synchronization, and event distribution. This multi-functional approach achieves real-time sync speed while avoiding the complexity of separate specialized systems for each function

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

Solution Approach 2:

API Gateway instances automatically publish and subscribe to event messages without requiring complex external coordination. The system self-configures by retrieving execution plans from cloud storage and autonomously manages its own synchronization subscriptions, reducing overall system complexity

Inventive Principle:
Principle #25Self-service

3Productivity

If event-based communication is implemented for asynchronous operation, then system efficiency is improved, but implementation complexity increases

Engineering Contradiction:
Improvesystem efficiencyVSAvoidimplementation complexity
Core Design Contradiction:
ProductivityVSDevice complexity

Solution Approach 1:

The event-based communication system implements automatic feedback loops where API Gateway instances publish events to cloud storage and immediately subscribe to receive notifications. This self-feedback mechanism enables asynchronous operation and improved productivity while keeping implementation complexity manageable through standardized event message patterns

Inventive Principle:
Principle #23Feedback

Data Source

PatentUS12579293B2Systems and methods for API gateway synchronization with cloud storage
Publication Date: 2026.03.17 RAKUTEN SYMPHONY INC
  • US12579293B2 patent drawing
  • US12579293B2 patent drawing
  • US12579293B2 patent drawing

AI summary

Provided are a method, system, and device for onboarding an API using an API gateway, the method may include: receiving, by a traffic manager (TM) module, an event message originating from an all-in-one (AIO) module of a first datacenter; receiving, by the TM module, execution plan data from a cloud storage object, wherein the execution plan data may be used to configure load throttling of an API; forwarding, by the TM module, the event message to a key manager (KM) module; receiving, by the TM module, a security file event response from the KM module; forwarding, by the TM module, the event message to an API gateway; receiving, by the TM module, an API data event response from the API gateway; and sending, by the TM module, an API onboarding response event to the AIO module of the first datacenter based on the API data event response.