Software Architecture Building Better Applications with Architecture Best Practices
summary
Covers concrete architecture choices: when to keep a monolith, split into microservices with independent databases, or adopt micro frontends so Angular and React apps load independently; recommends an API Gateway for client abstraction and message queues vs HTTP for async needs. Gives a front-end folder layout (assets, shared, core, feature), CI/CD-driven style swaps, accessibility checks (contrast, alt text, header labels), and measurable payoffs: faster parallel development, easier testing, and reduced time to ship new features.
AI-written summary · about
chapters (10)
- 0:00Introduction and Finland context
- 2:30Architecture patterns overview
- 3:57Monolithic vs microservices
- 5:45Hybrid architecture explained
- 6:30Micro front-end architecture
- 8:18Front-end architecture evolution
- 9:01Project structure best practices
- 11:12Accessibility in UI design
- 15:28Benefits of structured architecture
- 17:12Future of software architecture
related talks
36mApplication Architecture Patterns
40mHow to Design Good Large Applications
31mArchitectures for huge Angular based enterprise applications npm Packages, Monorepos and Micro Apps
20mArchitectures for huge Angular based Enterprise Applications...
50mThe Art of Front-end Architecture
01h 00mAgile Architecture
45mA Software Architect's Approach towards SPA Based Micro Apps
46mBUILDING ANTIFRAGILE APPLICATIONS