Realtime collaboration with Clojure - EuroClojure - Barcelona, 2015
•
0 likes•270 views
At Atlassian we are currently building services to enable realtime collaboration in both new and existing products. Of all technologies we could have chosen from we picked Clojure and ClojureScript. In this talk I will share the reasons for this choice, the benefits of running Clojure both on the server and on the client-side as well as our clustering solution built on top of core.async.
Recommended
Recommended
More Related Content
Similar to Realtime collaboration with Clojure - EuroClojure - Barcelona, 2015
Similar to Realtime collaboration with Clojure - EuroClojure - Barcelona, 2015 (20)
More from Leonardo Borges
More from Leonardo Borges (20)
Recently uploaded
Recently uploaded (20)
Realtime collaboration with Clojure - EuroClojure - Barcelona, 2015
- 1. Realtime collaboration with Clojure EuroClojure - Barcelona, 2015 Leonardo Borges @leonardo_borges www.atlassian.com www.leonardoborges.com
- 2. About ‣ Clojure engineer at Atlassian ‣ Functional Programming Advocate ‣ Founder of the Sydney Clojure User Group
- 3. About ‣ Clojure engineer at Atlassian ‣ Functional Programming Advocate ‣ Founder of the Sydney Clojure User Group ‣ Author of “Clojure Reactive Programming”
- 5. Stateless web servers are
- 7. user user user user user web server state user user user user web server web server load balancer
- 8. user user user user user DB user user user user web server load balancer state web server state web server state
- 12. Operational Transformation 101 ello BBarcelona! user server ello BBarcelona!
- 13. Operational Transformation 101 ello BBarcelona! user server ello BBarcelona! (ins 0 “H”) Hello BBarcelona!
- 14. Operational Transformation 101 ello BBarcelona! user server ello BBarcelona! (ins 0 “H”) (del 6) Hello BBarcelona! ello Barcelona!
- 15. Operational Transformation 101 ello BBarcelona! user server ello BBarcelona! (ins 0 “H”) (del 6) Hello BBarcelona! ello Barcelona!
- 16. Operational Transformation 101 ello BBarcelona! user server ello BBarcelona! (ins 0 “H”) (del 6) Hello BBarcelona! ello Barcelona! HelloBBarcelona! Hello Barcelona!
- 17. Operational Transformation 101 ello BBarcelona! user server ello BBarcelona! (ins 0 “H”) (del 6) Hello BBarcelona! ello Barcelona! (del 7)
- 18. Operational Transformation 101 ello BBarcelona! user server ello BBarcelona! (ins 0 “H”) (del 6) Hello BBarcelona! ello Barcelona! (del 7)Hello Barcelona! Hello Barcelona!
- 19. user user user user user DB user user user user web server load balancer state web server state web server state
- 20. Where do we send requests to?
- 21. Where do we send requests to? How do web nodes talk to each other?
- 22. Where do we send requests to? How do web nodes talk to each other? What happens when web nodes come up and down?
- 23. Where do we send requests to? How do web nodes talk to each other? What delivery guarantees are needed? What happens when web nodes come up and down?
- 24. Where do we send requests to? How do web nodes talk to each other? What delivery guarantees are needed? What happens when web nodes come up and down? What ordering guarantees are needed?
- 25. Where do we send requests to? How do web nodes talk to each other? What delivery guarantees are needed? What happens when web nodes come up and down? What ordering guarantees are needed?
- 26. Vert.x
- 30. Actors
- 31. Actors -State -Location Transparency -“At least once” delivery semantics -Ordering guarantees
- 32. Actors -State -Location Transparency -“At least once” delivery semantics -Ordering guarantees
- 33. Actors -State -Location Transparency -“At least once” delivery and ordering guarantees
- 34. Akka and Pulsar -Aka is awkward to use from Clojure -Clustering (in Pulsar) -JVM only -Fairness
- 35. Akka and Pulsar -Aka is awkward to use from Clojure -Clustering (in Pulsar) -JVM only -Fairness
- 36. Akka and Pulsar -Aka is awkward to use from Clojure -Clustering (in Pulsar) -JVM only -Fairness
- 37. Akka and Pulsar -Aka is awkward to use from Clojure -Clustering (in Pulsar) -JVM only -Fairness
- 38. user web server state entity Fairness user
- 39. useruser web server stateentity entity Fairness user user user user
- 40. Fairness
- 41. Options Summary Delivery Ordering Fairness End-to-End Vert.x Akka / Pulsar Distributed core.async (custom code)
- 42. Right, so what did we end up doing?
- 43. Multiplexer
- 47. Multiplexer Multiplexer endpoint endpoint web server state web server state duplex channel duplex channel duplex channel duplex channel
- 48. web server state Multiplexer Multiplexer endpoint endpoint web server state web server state duplex channel duplex channel duplex channel duplex channel
- 49. Multiplexer user load balancer web server state Multiplex web server state Multiplex web server state Multiplex
- 50. Multiplexer user load balancer web server state Multiplex web server state Multiplex web server state Multiplex
- 51. Multiplexer user load balancer web server state Multiplex web server state Multiplex web server state Multiplex
- 52. Multiplexer user load balancer web server state Multiplex web server state Multiplex web server state Multiplex
- 53. Multiplexer user load balancer web server state Multiplex web server state Multiplex web server state Multiplex
- 55. Aleph cluster -Client and Server network programming -Built on Netty and therefore asynchronous -Hazelcast for group membership
- 56. Aleph cluster -Client and Server network programming -Built on Netty (async #FTW) -Hazelcast for group membership
- 57. Aleph cluster -Client and Server network programming -Built on Netty (async #FTW) -Hazelcast for group membership
- 58. Aleph cluster + multiplexer -Distributed, end-to-end core.async channels -Message delivery and ordering guarantees -Fault tolerance -Fairness -Backpressure
- 59. Aleph cluster + multiplexer -Distributed, end-to-end core.async channels -Message delivery and ordering guarantees -Fault tolerance -Fairness -Backpressure
- 60. What’s next? CRDTs Production release Open-source Realtime data synchronisation as a service
- 61. What’s next? CRDTs Production release Open-source Realtime data synchronisation as a service
- 62. What’s next? CRDTs Production release Open-source Realtime data synchronisation as a service
- 63. What’s next? CRDTs Production release Open-source Realtime data synchronisation as a service
- 64. References Akka Pulsar Vert.x Aleph Jupiter OT algorithm Consistent Hashing Ring CRDTs in Riak akka.io bit.ly/actors-pulsar vertx.io/ aleph.io/ bit.ly/jupiterOT bit.ly/HashingRing bit.ly/CRDTRiak