Browser Micro-Application Container With Event-Driven Integration

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing software products face challenges in scalability, maintenance, integration with modern systems, and extensibility due to being legacy, monolithic, and lacking extensibility, leading to cumbersome add-ons and complex user interactions.

Innovation Solution

Implementing micro-application environments within a browser container using a plug-in that enforces maximum dependency criteria and anonymous event publication, facilitating easy scaling, maintenance, and integration with other applications.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If a monolithic legacy software product is used, then the product can be effective at certain tasks, but it becomes difficult to scale, maintain, and integrate into modern products

Engineering Contradiction:
Improveeffectiveness at tasksVSAvoidscalability and integrability
Core Design Contradiction:
ReliabilityVSAdaptability or versatility

Solution Approach 1:

The patent segments the monolithic legacy software into multiple independent micro-applications that can be developed, deployed, and maintained separately. Each micro-application encapsulates specific functionality, allowing the system to scale and integrate more easily while maintaining the reliability of individual components.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The patent creates a universal container environment that can host multiple micro-applications with different functionalities. This container provides a standardized interface and runtime environment that enables various micro-applications to work together, enhancing overall system adaptability while preserving individual component reliability.

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

2Ease of repair

If extensive knowledge of the whole system is required to implement changes, then the legacy product can be maintained, but it becomes difficult to extend and modify

Engineering Contradiction:
ImprovemaintainabilityVSAvoidextensibility
Core Design Contradiction:
Ease of repairVSAdaptability or versatility

Solution Approach 1:

By dividing the system into independent micro-applications, the patent allows changes to be made in isolation within specific micro-applications without requiring knowledge of the entire system. This maintains ease of repair for individual components while enabling easy extension through addition of new micro-applications.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The patent introduces an event bus and message passing mechanism as intermediaries between micro-applications. This allows micro-applications to interact through standardized events without requiring direct knowledge of internal system architecture, simplifying maintenance while enabling extensibility through event subscription.

Inventive Principle:
Principle #24Intermediary (Mediator)

3Adaptability or versatility

If functionality is implemented on an ad-hoc basis, then the product can be customized, but it leads to difficult maintenance and upkeep issues

Engineering Contradiction:
ImprovecustomizabilityVSAvoidmaintenance difficulty
Core Design Contradiction:
Adaptability or versatilityVSEase of repair

Solution Approach 1:

The patent segments ad-hoc functionality into discrete micro-applications with well-defined boundaries and interfaces. Each micro-application can be customized independently through configuration and event subscription, maintaining adaptability while improving maintenance through modular isolation.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The patent enables customization through configuration parameters and event subscription settings rather than code modifications. This allows ad-hoc functionality to be implemented by changing system parameters and configurations, maintaining customizability while significantly easing maintenance through non-invasive changes.

Inventive Principle:
Principle #35Parameter changes

4Adaptability or versatility

If multiple custom applications and add-ons are used, then the product can be extended, but users need to navigate between several applications to complete tasks

Engineering Contradiction:
ImproveextensibilityVSAvoiduser navigation complexity
Core Design Contradiction:
Adaptability or versatilityVSEase of operation

Solution Approach 1:

The patent merges multiple micro-applications into a unified container environment with a common user interface and shared event bus. This allows users to interact with multiple functionalities through a single interface, reducing navigation complexity while maintaining the extensibility of having multiple independent micro-applications.

Inventive Principle:
Principle #5Merging (Combining)

Solution Approach 2:

The container provides a universal interface that can access and coordinate multiple micro-applications through standardized events. This enables users to complete tasks that span multiple functionalities without navigating between separate applications, maintaining ease of operation while preserving system extensibility.

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

Data Source

PatentUS12566647B2System and method for implementing micro-application environments
Publication Date: 2026.03.03 THE TORONTO DOMINION BANK
  • US12566647B2 patent drawing
  • US12566647B2 patent drawing
  • US12566647B2 patent drawing

AI summary

A system, method, and computer readable medium for implementing micro-application environments is disclosed. The exemplary method includes providing a browser container (“browser”), and providing at least one micro-application for operating within the browser. The method includes providing a plug-in for the browser. The plug-in configured to listen to events originating in, or push events to, the at least one micro-application. The method includes storing, via the plug-in, documentation of events that each of the at least one micro-application subscribes to. The method includes determining, via the plug-in, occurrence of a first event, the first event being subscribed to by the at least one micro-application, and in response to determining the occurrence, generating, via the plug-in, a message to the at least one micro-application based on the event. The method includes executing, via the at least one micro-application, a new action in response to receiving the message.