Komparing Kotlin Server Frameworks
summary
Compares Ktor, HTTP4k, Javalin, Vert.x, Spring WebFlux and Micronaut by features and real tradeoffs: routing DSLs, coroutine vs reactive support, tracing/metrics availability (Zipkin vs missing OpenTracing), and cloud friendliness. Claims HTTP4k starts fastest and uses least memory, Vert.x and Netty-based stacks perform well, Spring is feature-rich but slowest, and JVM cold starts make Lambda costly unless using Graal/SubstrateVM native images. Highlights missing coroutine support in several frameworks and automatic JSON marshalling differences. Ktor (pure Kotlin) HTTP4k: fast startup, lambda-friendly Graal/SubstrateVM cuts cold starts dramatically.
AI-written summary · about
chapters (24)
- 0:00Start
- 0:33Komparing Kotlin Server Frameworks
- 1:31What is a Backend?
- 2:09Backends are
- 2:28Backends must
- 2:45What do you look for in a framework?
- 2:581. Kotlin!
- 4:112. Speed
- 4:44CORS (web)
- 5:04OAuth2/OIDC
- 5:31Testing
- 5:41Documentation
- 5:55Which frameworks?
- 7:14Ktor Coroutines
- 14:51Spring WebFlux
- 17:18Similarity?
- 17:32Code Portability
- 18:19API Facades
- 18:33Serverless?
- 19:06JVM Limitations
- 19:37How bad is it?
- 20:11Kotlin vs. Go
- 20:47But There's Hope
- 22:04All The Things!
related talks
39mEmbrace the Kotlin ecosystem at the back-end side
47mKotlin Server Framework Smackdown
03h 13mKotlin 1.4 Online Event, Day 4: server-side Kotlin
46mIntroduction to Ktor
53mServer-Side Development with Ktor
37mKotlin on the server with Ktor
46mMicroservices Kotlin Benchmark: coroutines, virtual threads... the Match!
40mFull-Stack Kotlin