Serverless Event Pipes for Cross-Format Service Integration

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Cloud-based services often experience compatibility issues due to differences in code, interfaces, or protocols, leading to latency and message failures when attempting to process data from services with different APIs or data formats, necessitating manual code integration that may not always be feasible.

Innovation Solution

A pipe is configured in a serverless computing environment to integrate services and applications using an event-driven architecture, allowing for automatic routing, filtering, transforming, batching, and buffering of events without requiring human-provided code, through a virtual communication channel that defines event structures and processing rules.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If services use different APIs, data formats, or protocols, then service diversity and functionality are improved, but compatibility and communication reliability deteriorate

Engineering Contradiction:
Improveservice diversityVSAvoidcommunication reliability
Core Design Contradiction:
Adaptability or versatilityVSReliability

Solution Approach 1:

The patent implements an event bus as an intermediary component that receives events from multiple services with different data formats and protocols, standardizes them into a unified event structure, and routes them to appropriate event destinations. This mediator layer enables services to maintain their unique interfaces while ensuring reliable communication through standardized event handling.

Inventive Principle:
Principle #24Intermediary (Mediator)

Solution Approach 2:

The system transforms events by changing their parameter representation from service-specific formats to a standardized event structure. The event bus modifies data format parameters, protocol parameters, and interface parameters to enable compatibility across diverse services while preserving the original service functionality.

Inventive Principle:
Principle #35Parameter changes

2Reliability

If manual code integration is provided to mitigate service differences, then communication compatibility is improved, but system complexity and maintenance burden increase

Engineering Contradiction:
Improvecommunication compatibilityVSAvoidsystem complexity
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The event bus provides self-service functionality by automatically detecting, standardizing, and routing events between services without requiring manual integration code. The system self-manages the complexity of protocol translation and data format conversion, freeing developers from writing and maintaining integration code while ensuring communication compatibility.

Inventive Principle:
Principle #25Self-service

3Speed

If services are tightly coupled through direct integration, then processing speed is improved, but system scalability and deployment flexibility deteriorate

Engineering Contradiction:
Improveprocessing speedVSAvoidsystem scalability
Core Design Contradiction:
SpeedVSAdaptability or versatility

Solution Approach 1:

The system segments the communication architecture by introducing an event bus that decouples services from direct point-to-point integration. Events are segmented into standardized units that can be independently processed, routed, and managed by the event bus, enabling services to operate independently while maintaining fast processing through efficient event routing.

Inventive Principle:
Principle #1Segmentation

4Loss of information

If comprehensive event data is transmitted between services, then data completeness is improved, but network overhead and processing load increase

Engineering Contradiction:
Improvedata completenessVSAvoidnetwork overhead
Core Design Contradiction:
Loss of informationVSLoss of energy

Solution Approach 1:

The event bus extracts only the essential event data needed for processing and transmission, separating critical event information from redundant service-specific data. By extracting and standardizing only the necessary event parameters, the system maintains data completeness for event processing while reducing network overhead and processing load from unnecessary data transmission.

Inventive Principle:
Principle #2Taking out (Extraction)

Data Source

PatentUS12360829B1Defining event data in an event-driven architecture
Publication Date: 2025.07.15 AMAZON TECH INC
  • US12360829B1 patent drawing
  • US12360829B1 patent drawing
  • US12360829B1 patent drawing

AI summary

Techniques for a service provider network to communicatively couple services and/or applications in a serverless computing environment. A pipe component can configure a pipe to integrate two services by transmitting data between services and/or applications using the pipe. The pipe may also be configured to transform how a service processes an event, control timing of event transmissions using the pipe, define an event structure for an event, and/or batch events. Pipes enable an application or service to exchange data with a variety of services provided by the service provider network while controlling what type of data is generated, stored, or transmitted.