MIGRATING TO CLOJURE. SO MUCH FN
summary
Gradual migration replaces a Rails monolith serving five million monthly visitors with Clojure widgets that are two functions widgets as fetch+view, run alongside Ruby in a single JVM with a thin data-translation layer, and render independently so immutability lets a simple swap from map to pmap parallel rendering speed up pages. Templates convert HTML to data via nlife, live-editing uses nREPL over TCP so production fixes and interactive development happen in-process, and infrastructure dropped from ~50–60 Ruby servers to about 12 JVMs while traffic grew.
AI-written summary · about
chapters (36)
- 0:00Intro
- 0:50History
- 8:35Immutability
- 12:15Templating
- 14:00Data Structures
- 14:35Ripple
- 15:27Immersion
- 16:18Ripple availability
- 17:25Closure community
- 18:01JVM
- 18:33Ruby
- 19:23Writing code
- 19:58Job adverts
- 20:32People
- 20:59Microservices
- 21:45Summary
- 22:18New projects
- 23:10Conclusion
- 24:29Productivity
- 25:00Rails vs Java
- 27:17SEO
- 27:39Switching from Ruby to Closure
- 29:19What I dont understand
- 30:41The adventures in hiring
- 31:10Anything else
- 31:27Do you still like Ruby
- 31:51Closure is Lisp
- 32:17Nested code structures
- 34:02Closure
- 34:23Ruby vs Closure
- 35:29Data types
- 35:52Functional Geekery
- 37:03Enclosure Testing
- 37:29Isolation
- 38:28Rails vs Closure
- 38:38Its not a simple decision
related talks
40mclojure is my favourite ruby
31mClojure at 4,000 msg/s-What We Learned, Loved, and Loathed
34mClojure by neophyte
38m"Growing Data Center networking mgmt UI using ClojureScript, Reagent and re-frame"
01h 15mEffective Programs - 10 Years of Clojure
37mClojure Remixed: Pyroclast Data Processing
21mA Clojure Carol: Three Clojure Web Development A-Ha Moments
40mGetting 50,000 Companies on Board with Clojure
