Philosophical Architecture in Grails
summary
Argues Grails’ default end‑tier, data‑centric approach causes coupling and “service spaghetti” and proposes explicit domain boundaries implemented as simple interfaces, an event‑based (declarative) communication style, and replaceable implementations. Uses Grails + Spring, Spock + Geb/Selenium, and a public GitHub sample to show a running app with a stubbed workflow, an event stream that can be replayed, and a passing UI functional test — notably no DB required for UI tests.
AI-written summary · about
chapters (25)
- 0:00Start
- 0:11Philosophical Architecture (in Grails)
- 1:41Limitless Options For Design
- 1:53Only a few Architectures
- 7:01Coupling between tiers
- 9:49Data Centric N-Tier
- 11:08Architecture Is Philosophy
- 12:36What is your Philosophy?
- 13:52Plato's Theory of Ideal Forms
- 16:23Aristotlean Categories
- 18:55Utopia
- 20:18Pure Functional Programming
- 21:11SOA?
- 25:38Perfection is a lie
- 25:57The Stoics
- 28:10Pragmatism
- 28:33Reject Dogma
- 29:09Gather Proof
- 29:52Change is Real
- 31:40David, show them some code
- 32:17The Life Preserver' Approach
- 35:04What are Events?
- 35:19Asynchronous?
- 37:50Communication Centric
- 38:22No New Frameworks
