Recommended
More Related Content
Viewers also liked
Viewers also liked (18)
Similar to Concurrency: The Good, The Bad and The Ugly
Similar to Concurrency: The Good, The Bad and The Ugly (20)
Recently uploaded
Recently uploaded (20)
Concurrency: The Good, The Bad and The Ugly
- 1. Concurrency the Good, the Bad and the Ugly Dr. Roland Kuhn Akka Tech Lead Lgd. Viktor Klang Director of Engineering
- 12. The Good
- 13. The Good ✓Can be mapped onto CPUs
- 14. The Good ✓Can be mapped onto CPUs ✓"To the metal" — no overhead
- 15. The Good ✓Can be mapped onto CPUs ✓"To the metal" — no overhead ✓High degree of control
- 16. The Good ✓Can be mapped onto CPUs ✓"To the metal" — no overhead ✓High degree of control ✓Debugging
- 17. The Bad
- 21. The Bad ☣Heavyweight ☣Scarce ☣Diminishing returns ☣High wake-up latency
- 22. The Bad ☣Heavyweight ☣Scarce ☣Diminishing returns ☣High wake-up latency ☣Barebones / low-level
- 23. The Bad ☣Heavyweight ☣Scarce ☣Diminishing returns ☣High wake-up latency ☣Barebones / low-level ☣No means of recovery
- 24. The Ugly
- 25. The Ugly Is it threadsafe?
- 26. The Ugly Is it threadsafe? — Too coarse locks?
- 27. The Ugly Is it threadsafe? — Too coarse locks? — The right locks?
- 28. The Ugly Is it threadsafe? — Too coarse locks? — The right locks? — The right locking order?
- 29. The Ugly Is it threadsafe? — Too coarse locks? — The right locks? — The right locking order? Defensive error handling
- 30. The Ugly Is it threadsafe? — Too coarse locks? — The right locks? — The right locking order? Defensive error handling Do you understand JSR133?
- 34. The Good
- 36. The Good ✓Configurable execution ✓M:N task to thread ratio
- 37. The Good ✓Configurable execution ✓M:N task to thread ratio ✓Less JMM headache
- 38. The Bad
- 39. The Bad ☣How to handle errors?
- 40. The Bad ☣How to handle errors? ☣Dealing with blocking code
- 41. The Bad ☣How to handle errors? ☣Dealing with blocking code ☣Closing over mutable state
- 42. The Ugly
- 44. The Ugly Callback Hell Composing results
- 45. The Ugly Callback Hell Composing results Low reusability
- 46. The Ugly Callback Hell Composing results Low reusability Is it sync or async?
- 47. The Ugly Callback Hell Composing results Low reusability Is it sync or async? Debugging
- 51. The Good
- 52. The Good ✓Typesafe & non-blocking
- 53. The Good ✓Typesafe & non-blocking ✓Transactional
- 54. The Good ✓Typesafe & non-blocking ✓Transactional ✓Composable
- 55. The Bad
- 56. The Bad ☣Size to failure ratio
- 57. The Bad ☣Size to failure ratio ☣Retries are costly
- 58. The Ugly
- 59. The Ugly Dealing with side-effects
- 60. The Ugly Dealing with side-effects Dealing with failure
- 61. The Ugly Dealing with side-effects Dealing with failure Unpredictable performance
- 62. The Ugly Dealing with side-effects Dealing with failure Unpredictable performance Debugging
- 65. Java Future … and ExecutorService
- 66. The Good
- 69. The Bad
- 71. The Bad ☣Blocking composition ☣Guesstimation of deadlock
- 72. The Bad ☣Blocking composition ☣Guesstimation of deadlock ☣Futures are one-off
- 73. The Ugly
- 74. The Ugly Cancel other's Futures?
- 75. The Ugly Cancel other's Futures? Non-blocking requires polling
- 76. The Ugly Cancel other's Futures? Non-blocking requires polling Dealing with failure
- 79. Scala Future … with ExecutionContext
- 80. The Good
- 85. The Good ✓Typesafe ✓Non-blocking composition ✓Monadic ✓Freely sharable ✓Can recover from failure
- 86. The Bad
- 87. The Bad ☣Defers failures to downstream
- 88. The Bad ☣Defers failures to downstream ☣Closing over mutable state
- 89. The Bad ☣Defers failures to downstream ☣Closing over mutable state ☣No ordering of callbacks
- 90. The Bad ☣Defers failures to downstream ☣Closing over mutable state ☣No ordering of callbacks ☣Futures are one-off
- 91. The Ugly
- 92. The Ugly Callback Hell (use for instead)
- 93. The Ugly Callback Hell (use for instead) Debugging
- 96. Akka Dataflow
- 97. The Good
- 100. The Good ✓Typesafe ✓Non-blocking composition ✓Declarative using direct style
- 101. The Good ✓Typesafe ✓Non-blocking composition ✓Declarative using direct style ✓Deterministic
- 102. The Good ✓Typesafe ✓Non-blocking composition ✓Declarative using direct style ✓Deterministic ✓Non-local composition
- 103. The Bad
- 104. The Bad ☣CPS plugin error messages
- 105. The Bad ☣CPS plugin error messages ☣Limited applicability
- 106. The Bad ☣CPS plugin error messages ☣Limited applicability — Error handling
- 107. The Bad ☣CPS plugin error messages ☣Limited applicability — Error handling ☣Debugging
- 108. The Bad ☣CPS plugin error messages ☣Limited applicability — Error handling ☣Debugging ☣Futures are one-off
- 109. The Ugly
- 110. The Ugly CPS plugin error messages!!
- 113. Scala Async
- 114. The Good
- 115. The Good ✓Typesafe
- 117. The Good ✓Typesafe ✓Non-blocking composition ✓Declarative using direct style
- 118. The Bad
- 121. The Bad ☣Limited applicability ☣Debugging ☣Futures are one-off
- 122. The Ugly
- 126. Threads … and Queues
- 127. The Good
- 128. The Good ✓Typesafe
- 129. The Good ✓Typesafe ✓Blocking or Non-blocking
- 130. The Good ✓Typesafe ✓Blocking or Non-blocking ✓Back pressure possible
- 131. The Bad
- 132. The Bad ☣Heavyweight
- 135. The Bad ☣Heavyweight ☣Scarce ☣Diminishing returns ☣High wake-up latency
- 136. The Bad ☣Heavyweight ☣Scarce ☣Diminishing returns ☣High wake-up latency ☣Not really high-level
- 137. The Bad ☣Heavyweight ☣Scarce ☣Diminishing returns ☣High wake-up latency ☣Not really high-level ☣No means of recovery
- 138. The Ugly
- 143. Actors
- 144. The Good
- 148. The Good ✓Encapsulation ✓Supervision ✓Configurable execution ✓Location transparency
- 149. The Good ✓Encapsulation ✓Supervision ✓Configurable execution ✓Location transparency ✓Models real-world
- 150. The Good ✓Encapsulation ✓Supervision ✓Configurable execution ✓Location transparency ✓Models real-world ✓Require less guarantees
- 151. The Bad
- 152. The Bad ☣Untyped
- 153. The Bad ☣Untyped ☣Explicit lifecycle management
- 154. The Bad ☣Untyped ☣Explicit lifecycle management ☣Debugging
- 155. The Ugly
- 156. The Ugly Easy encapsulation violation
- 157. The Ugly Easy encapsulation violation Composition can be awkward
- 160. Rx & friends
- 161. The Good
- 162. The Good ✓Typesafe
- 164. The Good ✓Typesafe ✓Non-blocking composition ✓Reusable components
- 165. The Good ✓Typesafe ✓Non-blocking composition ✓Reusable components ✓Stream centric
- 166. The Bad
- 167. The Bad ☣Defers failures to downstream
- 168. The Bad ☣Defers failures to downstream ☣Explicit lifecycle management
- 169. The Bad ☣Defers failures to downstream ☣Explicit lifecycle management ☣"Glitches"
- 170. The Bad ☣Defers failures to downstream ☣Explicit lifecycle management ☣"Glitches" ☣Debugging
- 171. The Ugly
- 173. The Ugly Callback Limbo Inverted control flow
- 177. The Good
- 178. The Good ✓Typesafe
- 179. The Good ✓Typesafe ✓Declarative value composition
- 180. The Good ✓Typesafe ✓Declarative value composition ✓Direct style
- 181. The Good ✓Typesafe ✓Declarative value composition ✓Direct style ✓Deterministic
- 182. The Bad
- 184. The Ugly
- 185. The Ugly Side-effecting can introduce glitches
- 188. Summary 60
- 195. Compartmentalization ExecutionCoordination STM Java Future Conclusion Scala Future FRP Actors Dataflow & Async & Rx
- 196. Compartmentalization ExecutionCoordination STM Java Future Conclusion Scala Future FRP Actors Dataflow & Async & Rx Thread + Queue
- 197. Compartmentalization ExecutionCoordination STM Java Future Conclusion Scala Future FRP Actors Dataflow & Async & Rx Thread + Queue Executor
- 198. Compartmentalization ExecutionCoordination STM Java Future Conclusion Scala Future FRP Actors Dataflow & Async & Rx Thread + Queue Executor Thread + Locks
- 199. Conclusion
- 200. Conclusion Pick
- 201. Conclusion Pick your
- 203. E0F