Physical Blocks for Microservice Composition

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

There is no systematic way to guide the development of cloud-born services with low complexity, and software designers lack the skills to create scalable, adaptive, and componentized applications in the microservices approach, making it challenging to combine atomic services into microservices effectively.

Innovation Solution

A composition system that uses physical blocks representing atomic services, allowing users to arrange and connect these blocks to dynamically compose microservices, with the system detecting connections, identifying necessary interfaces, and deploying the microservice upon successful configuration, while providing error notification and haptic feedback for assembly and modification.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Ease of manufacture

If traditional software development methods are used to create microservices, then developers can build applications with existing skills, but the process lacks systematic guidance and becomes complex and difficult to scale

Engineering Contradiction:
Improveease of creating microservicesVSAvoidcomplexity of microservice architecture
Core Design Contradiction:
Ease of manufactureVSDevice complexity

Solution Approach 1:

The patent uses physical blocks as tangible copies or representations of atomic services. Each physical block corresponds to a software component, allowing developers to manipulate physical objects that mirror the digital microservice architecture. This copying approach simplifies the development process by providing a concrete, systematic method for designing complex software systems.

Inventive Principle:
Principle #26Copying

Solution Approach 2:

The patent divides the microservice architecture into discrete atomic services, each represented by an individual physical block. This segmentation allows developers to independently design, arrange, and modify individual services without affecting the entire system, making the complex architecture more manageable and easier to manufacture.

Inventive Principle:
Principle #1Segmentation

2Ease of operation

If physical blocks are used to represent atomic services, then the development process becomes more intuitive and systematic, but the device complexity increases due to physical components

Engineering Contradiction:
Improveease of arranging and configuring microservicesVSAvoidcomplexity of physical block system
Core Design Contradiction:
Ease of operationVSDevice complexity

Solution Approach 1:

The physical blocks are designed as universal components that can represent any atomic service through standardized interfaces and connection mechanisms. Each block serves multiple functions: it represents a service, provides connection points for integration, and can be systematically arranged to form different microservice architectures. This universality reduces the need for specialized components for each service type.

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

Solution Approach 2:

The patent introduces physical blocks as intermediary objects between the developer's intent and the digital microservice implementation. These blocks serve as a mediator that translates physical arrangements into software configurations, making the development process more intuitive while managing the complexity through a standardized interface layer.

Inventive Principle:
Principle #24Intermediary (Mediator)

3Productivity

If manual configuration of atomic services is performed without systematic guidance, then developers have flexibility in design, but the process becomes time-consuming and error-prone

Engineering Contradiction:
Improvespeed of microservice deploymentVSAvoidtime for configuring and debugging microservices
Core Design Contradiction:
ProductivityVSLoss of time

Solution Approach 1:

The patent incorporates preliminary action by pre-defining standardized interfaces and connection protocols on the physical blocks before the actual microservice configuration begins. The blocks are designed with predetermined connection points and communication protocols, allowing developers to quickly assemble and deploy microservices without time-consuming customization or debugging of interfaces.

Inventive Principle:
Principle #10Preliminary action

Data Source

PatentUS10346338B2Use of physical blocks to develop microservices
Publication Date: 2019.07.09 INTERNATIONAL BUSINESS MACHINE CORPORATION
  • US10346338B2 patent drawing
  • US10346338B2 patent drawing
  • US10346338B2 patent drawing

AI summary

A computer-implemented method includes detecting, using a processor, an arrangement of a plurality of blocks that are interconnected, where each block of the plurality of blocks is a physical block representing a corresponding atomic service. It is determined, using the processor, whether each atomic service represented by a block in the plurality of blocks is configured to communicate with each other atomic service represented by an other block with which the block is interconnected in the plurality of blocks. Based at least in part on determining that each atomic service represented by a block in the plurality of blocks is configured to communicate with each other atomic service represented by an other block with which the block is interconnected in the plurality of blocks, a microservice represented by the arrangement of the plurality of blocks is defined. The microservice is deployed.