This video was recorded at Lambda Days 2022 -https://www.lambdadays.org/lambdadays2022 Thread per request vs Thread pool per operation | Krzysztof Płachno - Scala Data Engineer at SwissBorg ABSTRACT When thinking about web applications designs there are two most common architectural paths that we can apply: the old good J2EE one of having one thread per request and newer, more FP-like of having separate thread pools for different operations in request fulfilment logic. Although, at functional programming conference, audience preference for one of those approaches is rather obvious, why not to have a closer look on both approaches and clearly get pros and cons of each? Talk meant to be a presentation of both architectural solutions, providing analysis their design motivations and practical consequences, pointing out advantages and drawbacks. All this to have nice comparison of them, that may help make valid decision on technology used of your next project. As concrete implementation examples Spring and Akka Http frameworks will be used. Disclaimer: The speaker codes Scala as part of my 9-5 job, still running my afterwork project in Java. Don't judge. At least before listening to the talk. • Timecodes 00:00 - 03:48 - Intro 03:49 - 05:52 - Web Application Characteristics 05:53 - 07:46 - Thread Mapping Models 07:47 - 08:49 - JVM 08:50 - 16:49 - Thread per Request 16:50 - 19:36 - Thread Pool per Operation 19:37 - 28:39 - Comparison 28:40 - 33:25 - Demo 33:26 - 44:43 - QnA • Follow us on social: Twitter: https://twitter.com/LambdaDays LinkedIn: https://www.linkedin.com/company/lambda-days/ • Looking for a unique learning experience? Attend the next Lambda Days conference near you! • SUBSCRIBE TO OUR CHANNEL https://www.youtube.com/channel/UC47eUBNO8KBH_V8AfowOWOw See what's coming up at: https://codesync.global