Web Content Management Server Parallel Job Execution

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Web service requests often require significant resources and time due to the complexity of processing data from multiple sources, which is not efficiently handled by traditional client/server models.

Innovation Solution

A method and device that utilize a web content management server to send jobs in parallel to multiple slave web services configured to execute tasks concurrently, generating a response by combining results from these services, thereby optimizing the processing of web service requests.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Productivity

If traditional client/server models are used to process web service requests, then resource consumption is high and processing time is long, but the system structure is simple and easy to implement

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

Solution Approach 1:

The patent divides a complex web service request into multiple independent jobs that can be processed in parallel. The master web service breaks down the request into separate tasks, assigns them to multiple slave web services, and aggregates the results. This segmentation enables concurrent processing without requiring complete redesign of the system architecture.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The patent introduces a master web service as an intermediary between the client and slave web services. This mediator coordinates the parallel processing by distributing jobs to multiple slave services and aggregating their responses. The intermediary pattern allows complex parallel processing while maintaining a simple client interface.

Inventive Principle:
Principle #24Intermediary (Mediator)

2Reliability

If multiple data sources are integrated to provide comprehensive web service responses, then the quality and completeness of responses improve, but the processing complexity and time increase significantly

Engineering Contradiction:
Improveresponse completenessVSAvoidprocessing time
Core Design Contradiction:
ReliabilityVSLoss of time

Solution Approach 1:

The patent segments the data retrieval process by assigning different data sources and processing tasks to separate slave web services. Each slave service independently retrieves and processes data from specific sources in parallel, eliminating sequential bottlenecks while ensuring comprehensive data collection from multiple sources.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The patent ensures continuous useful action by having multiple slave web services process different data sources simultaneously without idle time. The master service continuously receives and distributes jobs, and slave services continuously process and return results, maximizing resource utilization and reducing overall processing time.

Inventive Principle:
Principle #20Continuity of useful action

3Adaptability or versatility

If web services are designed to handle complex mashed-up content from various sources, then the functionality and versatility improve, but the resource consumption and processing overhead increase

Engineering Contradiction:
Improveservice functionalityVSAvoidresource consumption
Core Design Contradiction:
Adaptability or versatilityVSUse of energy by moving object

Solution Approach 1:

The patent segments complex web service functionality into independent, reusable slave web services that can be selectively invoked. Each slave service handles specific data retrieval or processing tasks, allowing the system to achieve high versatility through composition of specialized services rather than monolithic complex services, reducing overall resource consumption.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The patent creates a universal master web service framework that can coordinate multiple specialized slave services for different functions. This multi-functional architecture allows the same master service to handle various types of complex requests by dynamically selecting and coordinating appropriate slave services, achieving versatility without duplicating processing logic.

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

Data Source

PatentUS10218775B2Methods for servicing web service requests using parallel agile web services and devices thereof
Publication Date: 2019.02.26 USABLENET INC
  • US10218775B2 patent drawing
  • US10218775B2 patent drawing
  • US10218775B2 patent drawing

AI summary

A method, non-transitory computer readable medium, and web content management server device that sends each of a plurality of jobs requiring execution in order to service a received web service request to one of a plurality of slave web services configured to execute the plurality of jobs in parallel. A response from each of the plurality of slave web services is received. A web service response is generated based on the received responses. The generated web service response is provided in response to the received web service request.