Enterprise Messaging Bus with Shims for Build Automation
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing software development and packaging processes lack integration among different services due to the absence of a common native format of communication, preventing the creation of automated processes across these services.
Innovation Solution
The implementation of an enterprise messaging bus coupled with service-specific shims that translate messages between services and the messaging bus, allowing services to communicate without requiring changes to their native formats, enabling seamless interaction and automation across different services.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Extent of automation
If different services use their own native communication formats, then each service maintains its operational independence and reliability, but the services cannot be integrated to enable automated processes
Solution Approach 1:
The patent introduces an enterprise messaging bus as an intermediary component that sits between different services with native communication formats. The messaging bus provides a standardized message format and routing mechanism that enables integration without requiring changes to the existing services. Services publish messages to the bus in their own formats, and the bus handles the coordination and delivery, thus enabling automated processes while maintaining service independence.
2Extent of automation
If services are integrated through a common communication format, then automated processes can be built across services, but the services must be modified to accommodate the new format
Solution Approach 1:
The messaging bus acts as a mediator that handles format conversion and coordination without requiring modifications to the existing services. Services continue to operate with their native formats, publishing and consuming messages as before. The bus provides the integration layer that enables cross-service automation while preserving the original service implementations.
Solution Approach 2:
The enterprise messaging bus provides a universal communication platform that can handle multiple different service formats simultaneously. It offers standardized message routing, delivery guarantees, and coordination mechanisms that work across diverse service types, enabling cross-service automation through a single multi-functional infrastructure.
3Adaptability or versatility
If an enterprise messaging bus is introduced to integrate services, then automated processes and service communication are enabled, but the system architecture becomes more complex
Solution Approach 1:
The messaging bus consolidates multiple communication functions into a single universal platform. It provides message routing, delivery guarantees, format handling, and coordination mechanisms that would otherwise require separate implementations for each service pair. This multi-functional approach enables versatile service communication while managing architecture complexity through consolidation.
Data Source
AI summary
A build system executes a build process using an enterprise messaging bus, a plurality of services, and a plurality of shims, where each of the services do not natively communicate with the enterprise messaging bus. A shim processes a message between a service and an enterprise message bus. The shim further communicates the processed message between the service and the enterprise message bus. The shim includes a receive shim that receives messages from the enterprise message bus, converts the received message into a format native to the service, and forwards the converted message to the service. The shim also includes a transmit shim that receives messages from the service, converts the received message into a format native to the enterprise message bus, and forwards the converted message to the enterprise message bus.