RESTful Framework for Modular Microservices in Monolithic Systems

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 software modules, enabling modular communication approaches and creating microservices for non-time-sensitive operations within a monolithic system.

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 patent segments the monolithic software system by introducing a RESTful framework that enables modular communication between software modules. This allows the system to maintain the performance benefits of a monolith while gaining the scalability and modularity of distributed components through standardized HTTP-based interfaces.

Inventive Principle:

Principle #1Segmentation

2Adaptability or versatility

If software modules are added to increase functionality, then adaptability improves, but coupling between modules increases and productivity decreases

Engineering Contradiction:

ImprovefunctionalityVSAvoidfeature velocity

Core Design Contradiction:

Adaptability or versatilityVSProductivity

Solution Approach 1:

The patent implements a universal RESTful communication framework that enables different software modules to interact through standardized HTTP operations. This universal interface reduces coupling between modules while maintaining functionality, as modules can be developed independently using common REST conventions for data exchange and service interaction.

Inventive Principle:

Principle #6Universality (Multi-functionality)

3Adaptability or versatility

If microservices are created for non-time-sensitive operations, then modularity improves, but system complexity increases

Engineering Contradiction:

ImprovemodularityVSAvoidsystem complexity

Core Design Contradiction:

Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The patent introduces a RESTful framework as an intermediary layer between monolithic and microservices architectures. This mediator enables selective modularization of non-time-sensitive operations through standardized HTTP interfaces while keeping time-critical path operations within the optimized monolith, thereby managing system complexity through a clear architectural boundary.

Inventive Principle:

Principle #24Intermediary (Mediator)

Data Source

PatentUS20220393941A1Geo Tagging for advanced analytics and policy enforcement on remote devices

Publication Date: 2022.12.08 ZSCALER INC

AI summary

Systems and methods implemented in a node in a cloud-based system include loading a data structure into memory, wherein the data structure includes cities mapped to cells where the cells cover all of the Earth; receiving a call with a given latitude and longitude of a user device; finding a closest city to the given latitude and longitude utilizing the data structure; and providing the closest city in response to the call. The systems and methods can also include utilizing the closest city for policy in the cloud-based system for the user device.