Real applications,
built with Storm.
The same movie browser on the public IMDB dataset, built on Ktor and Spring Boot, in Kotlin and Java, with GraalVM native-image variants. Each one shows idiomatic Storm in a real project. Clone one and run it with Docker and Gradle.
//Example projectsServer-rendered movie browsers: entities, repositories, projections, pagination, transactions, and tests in a working application.
Storm Movies · Kotlin + Ktor→
A server-rendered movie browser on Ktor 3 with the Storm plugin: automatic repository registration, service wiring with ktor-server-di, coroutine-native transactions, kotlinx.serialization for the JSON APIs, and Playwright-driven interface tests.
KotlinKtor 3
Storm Movies · Kotlin + Spring Boot 4→
The same movie browser on Spring Boot 4 with immutable data-class entities, metamodel-based queries, coroutine-native transactions, and schema validation. PostgreSQL with Flyway migrations; repository tests on H2 with storm-test.
KotlinSpring Boot 4
Storm Movies · Java + Spring Boot 4→
The Java flavor on Java 21: immutable record entities, metamodel-based queries, Spring-managed transactions, and schema validation. No JPA, no proxies, no persistence context.
Java 21Spring Boot 4
//GraalVM native imagesThe same applications compiled to native binaries: sub-second startup, the data layer registered by Storm itself, verified by the same Playwright suites.
Storm Movies · Spring Boot 4 · GraalVM→
The Spring Boot movie browser as a native image: entities and scanned repositories registered automatically through Storm's Spring AOT hints, startup around a quarter of a second, and the full Playwright suite running against the native binary.
KotlinSpring Boot 4GraalVM
Storm Movies · Ktor · GraalVM→
The Ktor movie browser as a native image: storm-core ships a GraalVM feature that registers entities and repositories from the compile-time type index, so the data layer needs no native configuration at all.
KotlinKtor 3GraalVM