High resiliency content delivery network backup mechanism for micro frontend web applications
A computing system receives, from a client device, a first request for access to a single page application associated with the computing system. A gateway of the computing system intercepts the first request before it reaches a shell service associated with the single page application. The gateway sends a second request for the single page application to the shell service. Based on the single page application request, the gateway determines that the shell service is experiencing a failure. Responsive to determining that the shell service is experiencing a failure, the gateway retrieves, from a content delivery network, a uniform resource locator (URL) associated with a time-lapse hypertext markup language (HTML) of the single page application. The gateway redirects the client device to the time-lapse HTML of the single page application using the URL.
1. A method performed by a computing system comprising:
intercepting a first request from a client device for a single page application before the first request reaches a service associated with the single page application;
sending a second request for the single page application to the service;
determining that the service is experiencing a failure;
responsive to determining that the service is experiencing the failure, retrieving a uniform resource locator (URL) associated with a time-lapse hypertext markup language (HTML) of the single page application; and
redirecting, based on the URL, the client device to the time-lapse HTML of the single page application.
2. The method of claim 1 , further comprising:
periodically calling, by an automated bot, the service for the single page application;
capturing, by the automated bot, dynamically generated time-lapse single page applications corresponding to the single page application; and
storing, by the automated bot, the dynamically generated time-lapse single page applications on a content delivery network.
3. The method of claim 2 , wherein retrieving the URL associated with the time-lapse HTML of the single page application comprises:
receiving, from the content delivery network, the URL Associated with a dynamically generated time-lapse single page application that is user agnostic.
4. The method of claim 1 , wherein determining that the service is experiencing the failure comprises:
analyzing a response from the service; and
determining that an error is present.
5. The method of claim 1 , wherein determining that the service is experiencing the failure comprises:
determining that the service failed to respond to the single page application request within a threshold time period for response.
6. The method of claim 1 , further comprising:
continually monitoring the service;
determining that the service has been restored; and
based on the determination that the service has been restored, serving, to the client device, live traffic from the service.
7. The method of claim 1 , further comprising:
fetching user specific context data from the client device; and
integrating the user specific context data with the time-lapse HTML of the single page application.
8. The method of claim 1 , further comprising:
bootstrapping a plurality of widgets to the time-lapse HTML of the single page application to navigate through the time-lapse HTML of the single page application.
9. The method of claim 1 , further comprising:
intercepting another request from the client device for access to a second single page application before the request reaches a second service associated with the second single page application.
10. The method of claim 9 , further comprising:
determining that the second service is not experiencing a failure; and
based on the determining, providing the client device with a hypertext markup language (HTML) file associated with the second service.
11. A system comprising:
a processor; and
a memory having one or more instructions stored thereon, which, when executed by the processor, causes the system to perform operations comprising:
intercepting a first request from a client device for a single page application before the first request reaches a service associated with the single page application;
sending a second request for the single page application to the service;
determining that the service is experiencing a failure;
responsive to determining that the service is experiencing the failure, retrieving a uniform resource locator (URL) associated with a time-lapse hypertext markup language (HTML) of the single page application; and
redirecting, based on the URL, the client device to the time-lapse HTML of the single page application.
12. The system of claim 11 , wherein the operations further comprise:
periodically calling, by an automated bot, the service for the single page application;
capturing, by the automated bot, dynamically generated time-lapse single page applications corresponding to the single page application; and
storing, by the automated bot, the dynamically generated time-lapse single page applications on a content delivery network.
13. The system of claim 12 , wherein retrieving the URL associated with the time-lapse HTML of the single page application comprises:
receiving, from the content delivery network, the URL Associated with a dynamically generated time-lapse single page application that is user agnostic.
14. The system of claim 11 , wherein determining that the service is experiencing the failure comprises:
analyzing a response from the shell service; and
determining that an error is present.
15. The system of claim 11 , wherein determining that the service is experiencing the failure comprises:
determining that the service failed to respond to the single page application request within a threshold time period for response.
16. The system of claim 11 , wherein the operations further comprise:
continually monitoring the service;
determining that the service has been restored; and
based on the determination that the service has been restored, serving, to the client device, live traffic from the service.
17. The system of claim 11 , wherein the operations further comprise:
fetching user specific context data from the client device; and
integrating the user specific context data with the time-lapse HTML of the single page application.
18. The system of claim 11 , wherein the operations further comprise:
bootstrapping a plurality of widgets to the time-lapse HTML of the single page application to navigate through the time-lapse HTML of the single page application.
19. The system of claim 11 , wherein the operations further comprise:
intercepting another request from the client device for access to a second single page application before the request reaches a second service associated with the second single page application.
20. The system of claim 19 , wherein the operations further comprise:
determining that the second service is not experiencing a failure; and
based on the determining, providing the client device with a hypertext markup language (HTML) file associated with the second service.