Why Clojure?
summary
Company Amperity uses Clojure and ClojureScript as its core stack and runs more than a dozen Clojure developers across about 100 projects, claiming that Clojure keeps code small and data oriented while scaling. Built tooling includes line monolith to keep a single repo with per-project snapshots, Galaxy repl and vagrant experiments, finagle-based per-request overrides for side by side deploys, remote shared dev infra with msos isolation, and remon plus grafana for monitoring. Most efforts work but require nontrivial engineering investment.
AI-written summary · about
chapters (25)
- 0:00Start
- 3:49Why Clojure?
- 6:28Smart People?
- 8:39Remote Working
- 9:26So What's the Downside?
- 10:32Terrariums!
- 10:44No Clojure? No Problem!
- 12:54Lots of Clojure
- 13:38Project Hell
- 16:48Tools
- 18:49How Do They Talk to Each Other?
- 20:33Management
- 22:17Failure Tolerance
- 24:01Where is Service A?!
- 26:00Workflow
- 27:12Vagrant
- 28:28Galaxy REPL
- 29:16Shared Development Environment
- 32:36Admin REPL
- 33:38Isolation
- 34:29Failing Fast
- 35:03Monitoring
- 36:45ClojureScript
- 38:36Team Feedback
- 39:13Company Fit
