Services Registry Message Broker for Cross-Firewall Synchronization
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
In B2B scenarios with multiple system landscapes separated by DMZs and firewalls, it is challenging to obtain an overview of connectivity entities and their relationships, complicating system lifecycle activities like configuration, preparation, and maintenance due to federated environments and independent system administration.
Innovation Solution
A system landscape utilizing multiple services registries that can exchange information, allowing publication and subscription of service information, with filtering and authentication mechanisms to manage data distribution across system borders, enabling synchronization and communication between Web Service providers and consumers.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If multiple services registries are deployed across system landscapes separated by firewalls, then system information can be distributed and accessed across organizational boundaries, but the complexity of managing connectivity entities and their relationships increases
Solution Approach 1:
The patent introduces intermediary components including a message broker, standardized message formats, and protocol translators that mediate communication between services registries across firewall boundaries. These intermediaries abstract the complexity of cross-system connectivity, enabling information distribution without requiring direct management of underlying network complexities.
Solution Approach 2:
The system divides the enterprise landscape into segmented services registries distributed across different organizational units and firewall zones. Each registry manages local connectivity entities independently while the message broker coordinates information exchange, allowing localized simplification while achieving global visibility.
2Loss of information
If services registries exchange detailed information about backend systems across firewalls, then comprehensive system overview is achieved, but security risks and data exposure increase
Solution Approach 1:
The patent implements local quality by allowing different levels of information detail to be published to different services registries based on security requirements. Sensitive backend system information can be masked, aggregated, or omitted in certain contexts while maintaining full detail locally, enabling comprehensive overview without uniform exposure of all systems.
Solution Approach 2:
Security intermediaries including authentication services, authorization intermediaries, and encrypted message channels are positioned between services registries and backend systems. These intermediaries enable information exchange while enforcing security policies, filtering sensitive data, and protecting against unauthorized access.
3Reliability
If independent system administration is maintained across federated environments, then system autonomy and security are preserved, but coordination of lifecycle activities becomes difficult
Solution Approach 1:
The patent implements a universal message broker and standardized event schema that can handle multiple lifecycle activities (deployment, configuration, maintenance, monitoring) across different systems and organizational units. This universal framework enables coordinated operations while preserving individual system administration autonomy, as the same mechanisms serve all coordination needs.
Solution Approach 2:
Services registries publish lifecycle events and status information to the message broker, which distributes this information to relevant subscribers across the enterprise. This feedback mechanism enables independent systems to remain aware of changes in other systems, facilitating coordinated lifecycle management without requiring centralized control.
Data Source
AI summary
Systems, computer products, and computer-implemented methods may be directed to publishing information about a service offered by a service provider at a first services registry. The information about the service can be communicated to a second services registry. An indication of a subscription to the service may be received by a service consumer from the second services registry. Information about the subscribed service can be communicated to the second services registry.