Empfohlen
Empfohlen
Weitere Àhnliche Inhalte
Andere mochten auch
Andere mochten auch (18)
Ăhnlich wie The Good, the Bad and the Ugly of Concurrency Models
Ăhnlich wie The Good, the Bad and the Ugly of Concurrency Models (20)
KĂŒrzlich hochgeladen
KĂŒrzlich hochgeladen (20)
The Good, the Bad and the Ugly of Concurrency Models
- 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 âConïŹgurable execution âM:N task to thread ratio
- 37. The Good âConïŹgurable 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 DataïŹow
- 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
- 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
- 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
- 149. The Good âEncapsulation âSupervision âConïŹgurable execution âLocation transparency âModels real-world
- 150. The Good âEncapsulation âSupervision âConïŹgurable 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 ïŹow
- 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 DataïŹow & Async & Rx
- 196. Compartmentalization ExecutionCoordination STM Java Future Conclusion Scala Future FRP Actors DataïŹow & Async & Rx Thread + Queue
- 197. Compartmentalization ExecutionCoordination STM Java Future Conclusion Scala Future FRP Actors DataïŹow & Async & Rx Thread + Queue Executor
- 198. Compartmentalization ExecutionCoordination STM Java Future Conclusion Scala Future FRP Actors DataïŹow & Async & Rx Thread + Queue Executor Thread + Locks
- 199. Conclusion
- 200. Conclusion Pick
- 201. Conclusion Pick your
- 203. E0F