That's My Monkey (...)
summary
Claims an architecture (domain driven design, event store + CQRS, distributed databases and message queues) that lets business logic be pure functions so systems scale with far less rewriting, asserting an Elixir and Elm stack can scale at least 10x compared to typical 2007-era frameworks. Examples include using Rabbit/Kafka and AWS (S3 API Gateway Lambda Dynamo Kinesis) and a refactor that removes 3600 lines from a 5000-line method, showing the approach actually ships fewer bugs and faster tests.
AI-written summary · about
chapters (27)
- 0:00Intro
- 1:55WHAT IS A SENIOR?
- 2:27WHAT IS A 10X DEVELOPER?
- 4:02WHAT IS VALUE?
- 5:05THE 1OX DEVELOPER
- 6:44CREATING 1 OX DEVELOPERS
- 7:44WHAT IS ANTI-VALUE?
- 11:17SIMPLE, DEMONSTRABLY CORRECT CODE
- 11:29WHAT IS COMPLEXITY?
- 13:28WHY COMPLEXITY IS BAD
- 14:52THE SIMPLICITY TEST
- 15:41EVALUATING TOOLS
- 16:22CODE REVIEWS
- 16:59PURE FUNCTIONS
- 20:45FUNCTIONAL-FIRST
- 31:44THERE ARE TWO TYPES OF PROGRAMMING LANGUAGES
- 35:31FUNCTIONAL PROGRAMMING LANGUAGES
- 36:20IDENTITY
- 38:03DATABASES
- 41:43REACTIVE SYSTEMS
- 44:22DOMAIN DRIVEN DESIGN
- 46:42THE FRONT END
- 47:47THE BACK END
- 49:42SOLVE FOR AN ARCHITECTURE
- 51:35DOMAIN SERVICES
- 52:39DISTRIBUTED COMPUTING
- 53:11SIMPLE, DEMONSTRABLY CORRECT SYSTEMS (FUNCTIONAL PROGRAMMING VERSION)
related talks
46mFrom a Ruby on Rails Monolith to Elixir and Elm Microservices
49mLarge-Scale Architecture: The Unreasonable Effectiveness of Simplicity
37mBuilt to last: A domain-driven approach to beautiful systems
01h 28mQ&A session with Mark Richards
01h 02mBuilding that glorious monolith. And carving it too.
44mAll the cool kids...
58mModernizing an existing system to take a more domain-driven approach
26mArchitecting for scale