How to Build a Hexagon: Pragmatic Architecture for Client Applications
summary
Presents a pragmatic architecture called “Hexagon” for client applications (SPA and React Native) to reduce technical debt caused by copying tutorial/demo code and heavy coupling to libraries. Explains concrete architectural rules and patterns the speaker developed over four years of building and refactoring apps, focusing on separating high-level from low-level code and defining clear integration points with third-party libraries.
AI-written summary · about
chapters (23)
- 0:00Introduction
- 1:32Speaker intro
- 2:58Client app mistakes
- 6:11First project case
- 15:50Second project challenges
- 17:37Hexagonal architecture basics
- 21:53Core layer
- 24:25Data providers layer
- 25:08Platform layer
- 27:14Framework role
- 30:44Error handling
- 31:05Redux details
- 36:57React adapters
- 39:29Data providers practice
- 40:54App layer structure
- 43:07Results and benefits
- 46:16Dev process improvements
- 47:42Code portability
- 49:11Performance gains
- 49:57Maintenance tips
- 51:01When to use
- 53:05Further reading
- 56:27Q&A
related talks
53mHexagonal Architecture in a Nodejs Project
19mHexagonal Architecture in Angular
45mHooked on the Hexagon, Node JS Didn't Really Help Me Stay Clean
51mHexagonal Architecture to the rescue
47mHexagonal Architecture in Practice, Live Coding That Will Make Your Applications More Sustainable
01h 51mHexagonal Architecturoplasty of a Backend: Open‑Code Operation
52mWhy not all hexagons have eight sides
50mHexagonal Architecture in Practice, Live Coding That Will Make Your Applications More Sustainable