RESTful Framework for Microservice Modularity and Latency

Resolve Bottlenecks,
Find Innovative SolutionsGenerate Solutions

Solution Overview

Problem

Monolithic software systems face challenges in scalability and modularity as complexity increases, leading to productivity issues and coupling between modules, which hinders efficient development and optimization.

Innovation Solution

A highly scalable RESTful framework and distributed Telemetry and Policy Gateway (TPG) using HTTP for communication between modules, enabling a modular approach that allows for geo-tagging of metrics and random device selection for measurement, facilitating higher modularity without decomposing the monolith.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Speed

If a monolithic software system is used, then hardware efficiency and latency are optimized, but scalability and modularity deteriorate as complexity increases

Engineering Contradiction:

ImprovelatencyVSAvoidmodularity

Core Design Contradiction:

SpeedVSAdaptability or versatility

Solution Approach 1:

The system is divided into independent microservices that communicate via RESTful HTTP interfaces. Each microservice encapsulates specific functionality (e.g., firewall module, proxy module, telemetry module) and can be developed, deployed, and scaled independently while maintaining low-latency communication through standardized protocols.

Inventive Principle:

Principle #1Segmentation

2Adaptability or versatility

If microservices are used, then modularity and scalability are improved, but inter-module communication latency increases

Engineering Contradiction:

ImprovemodularityVSAvoidinter-module communication latency

Core Design Contradiction:

Adaptability or versatilityVSSpeed

Solution Approach 1:

A universal RESTful HTTP communication framework is implemented across all microservices, providing standardized interfaces for data exchange. This universal approach enables any microservice to communicate with any other service through consistent protocols, reducing integration overhead and communication latency while preserving modularity.

Inventive Principle:

Principle #6Universality (Multi-functionality)

3Productivity

If the system is decomposed into microservices, then feature velocity and team productivity improve, but system complexity increases

Engineering Contradiction:

Improvefeature velocityVSAvoidsystem complexity

Core Design Contradiction:

ProductivityVSDevice complexity

Solution Approach 1:

A centralized API gateway and standardized RESTful communication layer act as intermediaries between microservices. This intermediary framework handles routing, authentication, and data normalization, reducing the complexity of inter-service communication while enabling teams to develop features independently at high velocity.

Inventive Principle:

Principle #24Intermediary (Mediator)

4Speed

If a monolithic system is used, then inter-module communication is optimized, but coupling between modules increases as new modules are added

Engineering Contradiction:

Improveinter-module communication speedVSAvoidcoupling between modules

Core Design Contradiction:

SpeedVSDevice complexity

Solution Approach 1:

Tight couplings between modules are extracted and replaced with loose couplings through RESTful HTTP interfaces. Each module is extracted as an independent microservice that communicates through standardized protocols, maintaining fast communication speeds while eliminating the coupling problems inherent in monolithic architectures.

Inventive Principle:

Principle #2Taking out (Extraction)

Data Source

PatentUS11582294B2Highly scalable RESTful framework

Publication Date: 2023.02.14 ZSCALER INC

AI summary

Systems and methods implemented in a node in a cloud-based system include operating a first cloud service that is implemented as a monolith system; operating a RESTful framework (Representational State Transfer web service) embedded in the cloud node; and operating one or more applications for one or more cloud services utilizing the RESTful framework, wherein the one or more applications are microservices. The RESTful framework utilizes Hypertext Transfer Protocol (HTTP) methods.