Composite Data Service Transactional Integrity via Merging

Resolve Bottlenecks,
Find Innovative SolutionsGenerate Solutions

Solution Overview

Problem

Web applications often require transactions that involve multiple data services, but individual data services may not natively support transactions, limiting the ability to implement complex data operations within web applications.

Innovation Solution

A composite data service is created using a set of software development tools that enables web applications to utilize multiple data services, allowing for transactional operations by specifying inputs, outputs, and relationships between services, with the data services execution engine handling calls and responses transparently to the end user.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If individual data services are used without composite service architecture, then service simplicity is maintained, but transactional capability across multiple services is lost

Engineering Contradiction:

Improvetransactional integrityVSAvoidservice architecture complexity

Core Design Contradiction:

ReliabilityVSDevice complexity

Solution Approach 1:

The patent merges multiple individual data services into a composite data service that orchestrates them as a unified transactional unit. The composite service combines the functionality of underlying services (invoice creation, payment processing, credit check) into a single service endpoint that can be invoked with one request and returns coordinated results, resolving the contradiction by providing transactional integrity without requiring the consumer to manage multiple service calls and their associated complexity

Inventive Principle:

Principle #5Merging (Combining)

Solution Approach 2:

The composite data service acts as an intermediary layer between the web application and individual data services. It mediates the interaction by receiving a single request from the application, coordinating calls to multiple underlying services, managing transactional state, and returning unified results. This intermediary pattern provides transactional capability while shielding the application from the complexity of direct multi-service orchestration

Inventive Principle:

Principle #24Intermediary (Mediator)

2Adaptability or versatility

If custom code is written to implement transactions across multiple data services, then transactional operations are achieved, but development time and maintenance complexity increase

Engineering Contradiction:

Improvetransactional operation capabilityVSAvoidservice implementation ease

Core Design Contradiction:

Adaptability or versatilityVSEase of manufacture

Solution Approach 1:

The composite data service enables self-service by providing pre-built transactional orchestration capabilities that can be consumed without custom implementation. The service automatically handles the coordination of multiple underlying services, transaction management, and error handling, allowing applications to gain transactional capability through simple service invocation rather than writing custom integration code

Inventive Principle:

Principle #25Self-service

Solution Approach 2:

The composite data service provides universal transactional orchestration capability that can handle multiple different underlying services through a single unified interface. It implements multi-functionality by supporting various transaction patterns (create invoice with payment, credit check before ordering, etc.) without requiring separate custom code for each scenario, thus providing adaptability while maintaining ease of implementation

Inventive Principle:

Principle #6Universality (Multi-functionality)

3Productivity

If multiple individual data service calls are made separately, then service granularity is maintained, but operational efficiency decreases

Engineering Contradiction:

Improvetransaction processing efficiencyVSAvoidservice invocation simplicity

Core Design Contradiction:

ProductivityVSEase of operation

Solution Approach 1:

The patent merges multiple separate service calls into a single composite service invocation. Instead of making individual calls to invoice creation, payment processing, and credit check services separately, the application makes one call to the composite service that internally orchestrates all necessary service calls, thereby improving productivity by reducing network latency and simplifying the operation to a single invocation

Inventive Principle:

Principle #5Merging (Combining)

Data Source

PatentUS10235146B1Method and mechanism for composite data service generation and implementation

Publication Date: 2019.03.19 EMC IP HLDG CO LLC

AI summary

In general, embodiments of the technology relate to implementing a composite data service in a web application. More specifically, embodiments of the technology enable a web application designer to create a composite data service that takes one or more inputs, generates one or more outputs, and that uses two or more data services (composite or non-composite) to generate the output(s) based on the one or more inputs. The composite data service, in one or more embodiments of the technology, enables a webpage to implement transactions that require the use of two or more individual data services.