Clubhouse Stackup 3/10/15

456 views

Published on

A quick overview of the Clubhouse stack.

Published in: Engineering
0 Comments
0 Likes
Statistics
Notes
  • Be the first to comment

  • Be the first to like this

No Downloads
Views
Total views
456
On SlideShare
0
From Embeds
0
Number of Embeds
5
Actions
Shares
0
Downloads
6
Comments
0
Likes
0
Embeds 0
No embeds

No notes for slide

Clubhouse Stackup 3/10/15

  1. 1. Kurt Schrader Co-Founder/CEO StackUp Mar 10, 2015
  2. 2. What is Clubhouse?
  3. 3. Powerful Tools for Engineering and Product Teams
  4. 4. See the big picture
  5. 5. Or the bigger picture
  6. 6. Clubhouse Stack
  7. 7. Why did we choose these technologies?
  8. 8. “If a painter were offered a brush that would make him a better painter, it seems to me that he would want to use it in all his paintings, wouldn't he?” -Paul Graham
  9. 9. Why Clojure?
  10. 10. ● It’s a Lisp ● It’s Functional ● Forces immutability and built for concurrency ● JVM Support
  11. 11. Clojure makes people happy
  12. 12. (Not all people)
  13. 13. Why use Javascript?
  14. 14. Why not use more Clojurescript?
  15. 15. Startups are an optimization problem
  16. 16. Our Stack
  17. 17. Elastic Load Balancer Elastic Load Balancer Javascript Javascript Clojure Clojure Datomic DynamoDB
  18. 18. Javascript Clojure Datomic Postgresql Development Stack
  19. 19. Why use Datomic? “The fully transactional, cloud-ready, distributed database.”
  20. 20. Started as an Experiment
  21. 21. We needed to store historical data
  22. 22. Datalog?
  23. 23. Simple and Thoughtful
  24. 24. Continuously reduce friction to move faster
  25. 25. Clubhouse Software, Inc. E: hello@clubhouse.io

×