More Related Content
Similar to Concurrency: The Good, The Bad and The Ugly
Concurrency: The Good, The Bad and The Ugly
- 1. Concurrency the Good, theBad and the Ugly Dr. Roland Kuhn Akka Tech Lead Lgd. Viktor Klang Director of Engineering
- 2.
- 3.
- 4.
- 5.
- 6.
- 7.
- 8.
- 9.
- 10.
- 11.
- 12.
- 13. The Good ✓Can bemapped onto CPUs
- 14. The Good ✓Can bemapped onto CPUs ✓"To the metal" — no overhead
- 15. The Good ✓Can bemapped onto CPUs ✓"To the metal" — no overhead ✓High degree of control
- 16. The Good ✓Can bemapped onto CPUs ✓"To the metal" — no overhead ✓High degree of control ✓Debugging
- 17.
- 18.
- 19.
- 20.
- 21. The Bad ☣Heavyweight ☣Scarce ☣Diminishing returns ☣Highwake-up latency
- 22. The Bad ☣Heavyweight ☣Scarce ☣Diminishing returns ☣Highwake-up latency ☣Barebones / low-level
- 23. The Bad ☣Heavyweight ☣Scarce ☣Diminishing returns ☣Highwake-up latency ☣Barebones / low-level ☣No means of recovery
- 24.
- 25. The Ugly Is itthreadsafe?
- 26. The Ugly Is itthreadsafe? — Too coarse locks?
- 27. The Ugly Is itthreadsafe? — Too coarse locks? — The right locks?
- 28. The Ugly Is itthreadsafe? — Too coarse locks? — The right locks? — The right locking order?
- 29. The Ugly Is itthreadsafe? — Too coarse locks? — The right locks? — The right locking order? Defensive error handling
- 30. The Ugly Is itthreadsafe? — Too coarse locks? — The right locks? — The right locking order? Defensive error handling Do you understand JSR133?
- 31.
- 32.
- 33.
- 34.
- 35.
- 36. The Good ✓Configurable execution ✓M:Ntask to thread ratio
- 37. The Good ✓Configurable execution ✓M:Ntask to thread ratio ✓Less JMM headache
- 38.
- 39. The Bad ☣How tohandle errors?
- 40. The Bad ☣How tohandle errors? ☣Dealing with blocking code
- 41. The Bad ☣How tohandle errors? ☣Dealing with blocking code ☣Closing over mutable state
- 42.
- 43.
- 44.
- 45. The Ugly Callback Hell Composingresults Low reusability
- 46. The Ugly Callback Hell Composingresults Low reusability Is it sync or async?
- 47. The Ugly Callback Hell Composingresults Low reusability Is it sync or async? Debugging
- 48.
- 49.
- 50.
- 51.
- 52. The Good ✓Typesafe &non-blocking
- 53. The Good ✓Typesafe &non-blocking ✓Transactional
- 54. The Good ✓Typesafe &non-blocking ✓Transactional ✓Composable
- 55.
- 56. The Bad ☣Size tofailure ratio
- 57. The Bad ☣Size tofailure ratio ☣Retries are costly
- 58.
- 59. The Ugly Dealing withside-effects
- 60. The Ugly Dealing withside-effects Dealing with failure
- 61. The Ugly Dealing withside-effects Dealing with failure Unpredictable performance
- 62. The Ugly Dealing withside-effects Dealing with failure Unpredictable performance Debugging
- 63.
- 64.
- 65. Java Future … andExecutorService
- 66.
- 67.
- 68.
- 69.
- 70.
- 71. The Bad ☣Blocking composition ☣Guesstimationof deadlock
- 72. The Bad ☣Blocking composition ☣Guesstimationof deadlock ☣Futures are one-off
- 73.
- 74. The Ugly Cancel other'sFutures?
- 75. The Ugly Cancel other'sFutures? Non-blocking requires polling
- 76. The Ugly Cancel other'sFutures? Non-blocking requires polling Dealing with failure
- 77.
- 78.
- 79. Scala Future … withExecutionContext
- 80.
- 81.
- 82.
- 83.
- 84.
- 85. The Good ✓Typesafe ✓Non-blocking composition ✓Monadic ✓Freelysharable ✓Can recover from failure
- 86.
- 87. The Bad ☣Defers failuresto downstream
- 88. The Bad ☣Defers failuresto downstream ☣Closing over mutable state
- 89. The Bad ☣Defers failuresto downstream ☣Closing over mutable state ☣No ordering of callbacks
- 90. The Bad ☣Defers failuresto downstream ☣Closing over mutable state ☣No ordering of callbacks ☣Futures are one-off
- 91.
- 92. The Ugly Callback Hell(use for instead)
- 93. The Ugly Callback Hell(use for instead) Debugging
- 94.
- 95.
- 96.
- 97.
- 98.
- 99.
- 100. The Good ✓Typesafe ✓Non-blocking composition ✓Declarativeusing direct style
- 101. The Good ✓Typesafe ✓Non-blocking composition ✓Declarativeusing direct style ✓Deterministic
- 102. The Good ✓Typesafe ✓Non-blocking composition ✓Declarativeusing direct style ✓Deterministic ✓Non-local composition
- 103.
- 104. The Bad ☣CPS pluginerror messages
- 105. The Bad ☣CPS pluginerror messages ☣Limited applicability
- 106. The Bad ☣CPS pluginerror messages ☣Limited applicability — Error handling
- 107. The Bad ☣CPS pluginerror messages ☣Limited applicability — Error handling ☣Debugging
- 108. The Bad ☣CPS pluginerror messages ☣Limited applicability — Error handling ☣Debugging ☣Futures are one-off
- 109.
- 110. The Ugly CPS pluginerror messages!!
- 111.
- 112.
- 113.
- 114.
- 115.
- 116.
- 117. The Good ✓Typesafe ✓Non-blocking composition ✓Declarativeusing direct style
- 118.
- 119.
- 120.
- 121.
- 122.
- 123.
- 124.
- 125.
- 126.
- 127.
- 128.
- 129. The Good ✓Typesafe ✓Blocking orNon-blocking
- 130. The Good ✓Typesafe ✓Blocking orNon-blocking ✓Back pressure possible
- 131.
- 132.
- 133.
- 134.
- 135. The Bad ☣Heavyweight ☣Scarce ☣Diminishing returns ☣Highwake-up latency
- 136. The Bad ☣Heavyweight ☣Scarce ☣Diminishing returns ☣Highwake-up latency ☣Not really high-level
- 137. The Bad ☣Heavyweight ☣Scarce ☣Diminishing returns ☣Highwake-up latency ☣Not really high-level ☣No means of recovery
- 138.
- 139.
- 140.
- 141.
- 142.
- 143.
- 144.
- 145.
- 146.
- 147.
- 148.
- 149. The Good ✓Encapsulation ✓Supervision ✓Configurable execution ✓Locationtransparency ✓Models real-world
- 150. The Good ✓Encapsulation ✓Supervision ✓Configurable execution ✓Locationtransparency ✓Models real-world ✓Require less guarantees
- 151.
- 152.
- 153. The Bad ☣Untyped ☣Explicit lifecyclemanagement
- 154. The Bad ☣Untyped ☣Explicit lifecyclemanagement ☣Debugging
- 155.
- 156. The Ugly Easy encapsulationviolation
- 157. The Ugly Easy encapsulationviolation Composition can be awkward
- 158.
- 159.
- 160.
- 161.
- 162.
- 163.
- 164.
- 165. The Good ✓Typesafe ✓Non-blocking composition ✓Reusablecomponents ✓Stream centric
- 166.
- 167. The Bad ☣Defers failuresto downstream
- 168. The Bad ☣Defers failuresto downstream ☣Explicit lifecycle management
- 169. The Bad ☣Defers failuresto downstream ☣Explicit lifecycle management ☣"Glitches"
- 170. The Bad ☣Defers failuresto downstream ☣Explicit lifecycle management ☣"Glitches" ☣Debugging
- 171.
- 172.
- 173. The Ugly Callback Limbo Invertedcontrol flow
- 174.
- 175.
- 176.
- 177.
- 178.
- 179. The Good ✓Typesafe ✓Declarative valuecomposition
- 180. The Good ✓Typesafe ✓Declarative valuecomposition ✓Direct style
- 181. The Good ✓Typesafe ✓Declarative valuecomposition ✓Direct style ✓Deterministic
- 182.
- 183.
- 184.
- 185. The Ugly Side-effecting canintroduce glitches
- 186.
- 187.
- 188.
- 189.
- 190.
- 191.
- 192.
- 193.
- 194.
- 195.
- 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.
- 200.
- 201.
- 202.
- 203.