Akka - Possible Alternative for Spring?
summary
Compares Spring Web (RestTemplate) and Spring WebFlux (WebClient, Mono/Flux) to Akka HTTP and shows a small API with three endpoints: hello, wiremock (calls external mock), and a test route that reads path, query and header values and returns an info object. Demonstrates that raw Java Akka code requires explicit actor system and boilerplate and looks messy, while Play framework on top of Akka hides that boilerplate, injects the actor system, and uses routes files. Highlights Akka Streams for streaming large files without buffering and notes Akka licensing change and the Apache fork.
AI-written summary · about
chapters (11)
- 0:00Introduction and speaker intro
- 1:38Spring as Java standard
- 3:04Synchronous communication in Spring
- 7:21Asynchronous HTTP in Spring
- 13:51Akka framework overview
- 17:26Akka HTTP example
- 20:15Play framework on Akka
- 25:38Comparison and conclusion
- 27:52Akka licensing and drawbacks
- 29:23Akka streams for big files
- 30:50Q&A and closing remarks
related talks
01h 32mFrom Spring + Java to Spring + Akka - A Journey of Discovery
01h 01mThirst Quenching Streams for the Reactive Mind
01h 11mServlet or Reactive Stacks: The Choice is Yours. Oh No... The Choice is Mine! - Rossen Stoyanchev
47mReactive Spring
49mReactive Spring
01h 31mReactive Streams / Akka Streams
39mReactive for the Impatient (A Gentle Intro to Reactive Java)
46mAkka Streams & Reactive Streams in action