SPA

Single Page Application (commonly abbreviated as SPA) is an approach to building Web Applications whereby each separate view is derived from the same initial file or portal - commonly defined as an "index.html", "index.php" or "index.jsp", etc... to be served up from the root-level of their parent folder on most Web Servers without requiring further configuration (although other common naming conventions exist).

Resources

• Micro Frontends: https://micro-frontends.org
• Self-contained System (SCS): http://scs-architecture.org

Tutorials

• A Day at the "Automation SPA" (writing automated tests for an SPA) - Means Waiting for Elements to Disappear: https://applitools.com/blog/automation-spa-waiting-for-elements-to-disappear/

External Links

• wikipedia: Single-page application
• Single Page Application: advantages and disadvantages: https://stackoverflow.com/questions/21862054/single-page-application-advantages-and-disadvantages
• Single-Page vs. Multi-page UI Design: Pros & Cons: https://www.uxpin.com/studio/blog/single-page-vs-multi-page-ui-design-pros-cons/
• The disadvantages of Single Page Applications: https://adamsilver.io/articles/the-disadvantages-of-single-page-applications/
• Scaling with Microservices and Vertical Decomposition: https://dev.otto.de/2014/07/29/scaling-with-microservices-and-vertical-decomposition/
• Wait, what!? Our microservices have actual human users?: https://www.youtube.com/watch?v=pU1gXA0rfwc

See Also

RIA | PWA | Components | Widgets | React.js | Angular.js | SSI