Granted Patent B2

US 12,321,761 · App. 18/333,222 · Granted Jun 3, 2025

Inventors: John Bruno (Scottsdale, AZ); Sean Edward Falese (Jenkintown, PA); Arnaud Versini (Charlotte, NC)

Assignee: WELLS FARGO BANK, N.A.

G06F9/451G06F16/9577G06F16/958

Abstract

Claims (41)

1. A system, comprising:

at least one processor; and

non-transitory computer-readable storage storing instructions that, when executed by the at least one processor, cause the system to:

generate a hub and registry module programmed to:

determine if a plurality of micro front-ends is conformant with one or more experience rules, including indicating where a given micro front-end of the plurality of micro front-ends is located on a percentage scale from conformant to nonconformant, wherein the one or more experience rules define features and functions the given micro front-end must include to be conformant;

register one or more of the plurality of micro front-ends in response to determining the one or more of the plurality of micro front-ends are conformant with the one or more experience rules;

compose the one or more of the plurality of micro front-ends into an experience for a user;

monitor performance of the one or more of the plurality of micro front-ends within the experience, wherein the performance includes a response time for the one or more of the plurality of micro front-ends;

determine the response time for the one or more of the plurality of micro front-ends does not meet the one or more experience rules;

responsive to a determination that the response time for the one or more of the plurality of micro front-ends does not meet the one or more experience rules, update the one or more of the plurality of micro front-ends;

determine an updated version of the one or more of the plurality of micro front-ends fails to satisfy the one or more experience rules; and

responsive to a determination the updated version of the one or more of the plurality of micro front-ends fails to satisfy the one or more experience rules, revert the updated version of the one or more of the plurality of micro front-ends to a prior version of the one or more of the plurality of micro front-ends.

2. The system of claim 1 , wherein the hub and registry module is further programmed to:

determine a new version of the given micro front-end of the plurality of micro front-ends is conformant with the one or more experience rules;

store the new version of the micro front-end; and

replace a prior version of the micro front-end in the experience with the new version of the micro front-end.

3. The system of claim 1 , wherein the one or more experience rules are defined using a domain specific language.

4. The system of claim 3 , wherein the domain specific language is JavaScript Object Notation.

5. The system of claim 1 , wherein the hub and registry module is further programmed to generate a user interface on a display, the user interface comprising an overview of the plurality of micro front-ends.

6. The system of claim 5 , wherein the user interface comprises, for the given micro front-end, one or more of a current version, a version history, a deployment status, an availability status, and a conformance status.

7. The system of claim 6 , wherein the conformance status indicates one of a conformant status or a nonconformant status.

8. The system of claim 6 , wherein the conformance status comprises a report summarizing conformance and nonconformance with each of the one or more experience rules.

9. The system of claim 5 , wherein the user interface comprises a dependency graph.

10. A method for managing a contextual micro front-end experience, the method comprising:

receiving a micro front-end;

determining the micro front-end conforms with one or more experience rules;

registering the micro front-end;

storing the micro front-end;

deploying the micro front-end in response to a request to compose a contextual user experience;

monitoring performance of the micro front-end within the contextual user experience, wherein the performance includes a response time for the micro front-end;

determining the response time for the micro front-end does not meet the one or more experience rules;

responsive to a determination the response time for the micro front-end does not meet the one or more experience rules, updating the micro front-end;

determining an updated version of the micro front-ends fails to satisfy the one or more experience rules; and

responsive to determining the updated version of the micro front-ends fails to satisfy the one or more experience rules, revert the updated version of the micro front-ends to a prior version.

11. The method of claim 10 , further comprising determining a new version of the micro front-end is conformant with the one or more experience rules.

12. The method of claim 11 , further comprising storing the new version of the micro front-end.

13. The method of claim 12 , further comprising replacing a prior version of the micro front-end with the new version of the micro front-end.

14. The method of claim 12 , further comprising maintaining a prior version of the micro front-end along with the new version of the micro front-end.

15. The method of claim 11 , further comprising replacing a prior version of the micro front-end in an experience with the new version of the micro front-end.

16. The method of claim 15 , further comprising making a second determination the new version of the micro front-end is incompatible with the experience.

17. The method of claim 16 , further comprising generating a report summarizing the determination the new version of the micro front-end is incompatible with the experience.

Assignments (2)

Continuity (1)

References Cited (26)