Isomorphic web applications
summary
An isomorphic booking application implemented with Mithril.js renders the full HTML on the server (streaming from Node/Express) and then boots a single-page app on the client, keeping 90–95% of code shared between server and client. The approach reproduces identical routes and localization on both sides, injects preloaded state into a script tag, uses stateless JWTs for authentication, and addresses practical issues like routing tweaks, request plumbing, async component initialization, and avoiding SEO problems via server-side streaming render.
AI-written summary · about
chapters (18)
- 0:00Introduction
- 1:33Motivation for isomorphic apps
- 4:28SSR + SPA solution
- 7:21Live demo and docs
- 9:11Isomorphic benefits
- 10:59Mithril framework
- 14:38Why Mithril
- 15:00Isomorphic challenges
- 19:36Shared routing
- 21:52Component composition
- 24:00Component lifecycle
- 25:53Async data handling
- 28:01Uniform HTTP requests
- 29:03Shared state
- 31:56Auth and authorization
- 33:19Multilingual handling
- 35:50Internationalization
- 36:14Conclusion
related talks
43mIsomorphic JavaScript apps
44mRethinking Isomorphic JavaScript with SolidStart
39mTowards Universal JavaScript
58mUnderstand the Next Phase of Web Development
10mUniversal Apps: Architecture for the Modern Web
27mHTML Hypermedia APIs and Adaptive Web Design
55mTechnology agnostic microservices at SPA frontend
38mEmbrace the frontend revolution