Tear down this wall – rethink distributed systems

on YouTube ↗22m

" summary

Argues that treating a distributed system as one unified codebase speeds development: uses Clojure/ClojureScript, re-frame tests running on the JVM, clojure.spec and protocols to reuse specs across front end, WebSocket and backend, and a monorepo with Leiningen tricks to avoid dependency hell. Describes a generic feed reader that stores to S3 and services rebuilt locally for reliable reprocessing, reports faster iteration and fewer integration failures. re-frame JVM tests reuse clojure.spec across boundaries

AI-written summary · about

" chapters (13)

1. 0:00Intro
2. 0:24Most of us develop distributed systems
3. 2:10Do you know this architecture?
4. 2:40We even align our teams along these borders
5. 3:11We do not have a single architecture!
6. 3:43Unify creates a better environment: Focus on what is you current concern
7. 6:18Starting from unification, you may focus on different things.
8. 7:37Same principle, applied to a more complex system...
9. 8:09Break down one service into multiple smaller ones: Separation of concern
10. 12:24CLIC is our friend with Clojure crossing the platform gaps as easy as it could be Use CLIC
11. 15:41Spec your APIs - everywhere
12. 17:17Protocols to mock channels
13. 18:28and finally, use a monorepo

" related talks

• 34mClojure by neophytePaweł Kapała · JDD 2016
• 28mEvery Clojure Talk EverAlex Engelberg, Derek Slager · Clojure/conj 2018
• 38m"Growing Data Center networking mgmt UI using ClojureScript, Reagent and re-frame"Kirill Ishanov · Clojure/conj 2023
• 21mA Clojure Carol: Three Clojure Web Development A-Ha MomentsPaul S. Chun · reClojure 2022
• 01h 15mEffective Programs - 10 Years of ClojureRich Hickey · Clojure/conj 2017
• 27mThe Functional Final FrontierDavid Nolen · Clojure/West 2014
• 31mre-frame your ClojureScript applicationsShaun Mahood · Clojure/conj 2016
• 31mClojure at 4,000 msg/s-What We Learned, Loved, and LoathedNathan Barnett · Clojure/west 2017