Granted Patent B2

US 12,401,725 · App. 18/460,272 · Granted Aug 26, 2025

Inventors: Alexandre Porcelli Bakos (Westford, MA); Tiago Fernandes (Campinas, BR); Eder Ignatowicz (Cambridge, MA)

Assignee: Red Hat, Inc.

H04L67/147H04L67/02H04L67/51

Abstract

Claims (92)

1. A server comprising:

a processor; and

a memory including program code that is executable by the processor for causing the processor to:

receive a webpage request from a client device; and

in response to receiving the webpage request:

provide wrapper application code and micro-frontend code to the client device, the wrapper application code being for a wrapper application executable in a browser window of the client device, and the micro-frontend code being for a micro-frontend executable in the browser window of the client device; and

provide first message-handler code and second message-handler code to the client device, wherein the first message-handler code is for a first message handler executable in the browser window and the second message-handler code is for a second message handler executable in the browser window, the first message handler being associated with the wrapper application and configured to:

receive a request for data from the wrapper application, wherein the data is to be provided by a micro-frontend;

generate a request message based on the request, the request message including a unique identifier of the request;

transmit the request message via a communication channel to the second message handler associated with the micro-frontend;

receive a response message from the second message handler via the communication channel, wherein the response message includes the data and the unique identifier, the second message handler being configured to generate the response message based on the data from the micro-frontend; and

based on the unique identifier in the response message, provide the data to the wrapper application in a response to the request.

2. The server of claim 1 , wherein the first message handler is further configured to:

extract a message handler identifier (MHI) from the response message;

determine whether the MHI corresponds to the first message handler; and

in response to determining that the MHI corresponds to the first message handler, provide the data in the response message to the wrapper application.

3. The server of claim 2 , wherein the MHI is a first MHI, the response message is a first response message, and the first message handler is further configured to:

receive a second response message via the communication channel;

extract a second MHI from the second response message; and

in response to determining that the second MHI does not correspond to the first message handler, ignore the second response message.

4. The server of claim 1 , wherein the first message handler is configured to:

receive the request from the wrapper application;

generate the unique identifier for the request;

generate and return a browser object to the wrapper application based on the request;

generate a mapping that includes a correlation between the browser object and the unique identifier; and

subsequent to receiving the response message via the communication channel:

extract the unique identifier from the response message;

determine that the browser object corresponds to the response message based on the correlation in the mapping; and

in response to determining that the browser object corresponds to the response message, resolve the browser object with the data to provide the wrapper application with the data.

5. The server of claim 1 , wherein the communication channel is a messaging bus.

6. The server of claim 1 , wherein the request is in a first format, and wherein the request message is in a second format that is different from the first format.

7. The server of claim 1 , wherein the first message handler is separate from the wrapper application.

8. The server of claim 1 , wherein the second message handler is separate from the micro-frontend.

9. A method comprising:

receiving, by a server system, a webpage request from a client device; and

in response to receiving the webpage request:

providing, by the server system, wrapper application code and micro-frontend code to the client device, the wrapper application code being for a wrapper application executable in a browser window of the client device, and the micro-frontend code being for a micro-frontend executable in the browser window of the client device; and

providing, by the server system, first message-handler code and second message-handler code to the client device, wherein the first message-handler code is for a first message handler executable in the browser window and the second message-handler code is for a second message handler executable in the browser window, the first message handler being associated with the wrapper application and configured to:

receive a request for data from the wrapper application, wherein the data is to be provided by a micro-frontend;

generate a request message based on the request, the request message including a unique identifier of the request;

transmit the request message via a communication channel to the second message handler associated with the micro-frontend;

receive a response message from the second message handler via the communication channel, wherein the response message includes the data and the unique identifier, the second message handler being configured to generate the response message based on the data from the micro-frontend; and

based on the unique identifier in the response message, provide the data to the wrapper application in a response to the request.

10. The method of claim 9 , wherein the first message handler is further configured to:

extract a message handler identifier (MHI) from the response message;

determine whether the MHI corresponds to the first message handler; and

in response to determining that the MHI corresponds to the first message handler, provide the data in the response message to the wrapper application.

11. The method of claim 10 , wherein the MHI is a first MHI, the response message is a first response message, and the first message handler is further configured to:

receive a second response message via the communication channel;

extract a second MHI from the second response message; and

in response to determining that the second MHI does not correspond to the first message handler, ignore the second response message.

12. The method of claim 9 , wherein the wrapper application is configured to communicate with a plurality of micro-frontends in the browser window via a plurality of message handlers, wherein the plurality of micro-frontends including a first micro-frontend that is executable in a first context of the browser window and a second micro-frontend that is executable in a second context of the browser window, the second context being distinct from the first context.

13. The method of claim 12 , wherein the first context is an iFrame and the second context is external to the iFrame.

14. The method of claim 9 , wherein the first message handler is configured to:

receive the request from the wrapper application;

generate the unique identifier for the request;

generate and return a promise object to the wrapper application based on the request;

generate a mapping that includes a correlation between the promise object and the unique identifier; and

subsequent to receiving the response message via the communication channel:

extract the unique identifier from the response message;

determine that the promise object corresponds to the response message based on the correlation in the mapping; and

in response to determining that the promise object corresponds to the response message, resolve the promise object with the data to provide the wrapper application with the data.

15. The method of claim 9 , wherein the request specifies a function to be executed by the micro-frontend, and wherein the micro-frontend is configured to:

obtain the data by executing the function; and

return the data to the second message handler for communication to the first message handler.

16. A non-transitory computer-readable medium comprising program code that is executable by one or more processors for causing the one or more processors to:

receive a webpage request from a client device; and

in response to receiving the webpage request:

provide wrapper application code and micro-frontend code to the client device, the wrapper application code being for a wrapper application executable in a browser window of the client device, and the micro-frontend code being for a micro-frontend executable in the browser window of the client device; and

provide first message-handler code and second message-handler code to the client device, wherein the first message-handler code is for a first message handler executable in the browser window and the second message-handler code is for a second message handler executable in the browser window, the first message handler being associated with the wrapper application and configured to:

receive a request for data from the wrapper application, wherein the data is to be provided by a micro-frontend;

generate a request message based on the request, the request message including a unique identifier of the request;

transmit the request message via a communication channel to the second message handler associated with the micro-frontend;

receive a response message from the second message handler via the communication channel, wherein the response message includes the data and the unique identifier, the second message handler being configured to generate the response message based on the data from the micro-frontend; and

based on the unique identifier in the response message, provide the data to the wrapper application in a response to the request.

17. The non-transitory computer-readable medium of claim 16 , wherein the first message handler is configured to:

receive the request from the wrapper application;

generate the unique identifier for the request;

generate and return a promise object to the wrapper application based on the request;

generate a mapping that includes a correlation between the promise object and the unique identifier; and

subsequent to receiving the response message via the communication channel:

extract the unique identifier from the response message;

determine that the promise object corresponds to the response message based on the correlation in the mapping; and

in response to determining that the promise object corresponds to the response message, resolve the promise object with the data to provide the wrapper application with the data.

18. The non-transitory computer-readable medium of claim 16 , wherein the request message specifies a function name and arguments for a function to be executed by the micro-frontend, and wherein the micro-frontend is configured to:

obtain the data by executing the function based on the function name and arguments specified in the request message; and

return the data to the second message handler for communication to the first message handler.

19. The non-transitory computer-readable medium of claim 16 , wherein the second message handler is configured to:

receive the data from the micro-frontend; and

generate the response message based on the data; and

transmit the response message to the first message handler via the communication channel.

20. The non-transitory computer-readable medium of claim 16 , wherein the wrapper application is configured to communicate with a plurality of micro-frontends in the browser window via a plurality of message handlers, wherein the plurality of micro-frontends including a first micro-frontend that is executable in a first context of the browser window and a second micro-frontend that is executable in a second context of the browser window, the second context being distinct from the first context.

Assignments (2)

Continuity (2)

References Cited (53)