javalin
Creating tiny Java microservices with GraalVM (22MB total size)
Edit: Also, the HN title was edited by a HN mod, the title I used to post here was "Show HN: Basic Google Docs clone in Kotlin with WebSockets (tutorial)"
Creating a Google Docs clone with WebSockets
Show HN: My JVM web framework Javalin finally has async support
Show HN: Simple WebSocket server for Kotlin/Java/JVM
Show HN: cookieStore concept added in Javalin 0.5.0
I haven't seen auth solved this way in any other library/framework, so it would be great to get some feedback (both on the tutorial, and the concept of the AccessManager interface itself).
Show HN: Kotlin-tutorial for securing a REST API
Show HN: My Kotlin/Java REST Library Javalin Reaches v0.4.0 (CORS, Uploads, ++)
Show HN: Kotlin-tutorial for email sending via gmail
Show HN: Java-tutorial for email sending via gmail
Show HN: Kotlin-tutorial for forms and upload
Show HN: Java-tutorial for forms and upload
Show HN: Javalin, a Kotlin/Java REST API framework (big api changes)
The rest of the library will be ported to Kotlin if this issue is resolved, or and alternative solution is discovered.
I guess the biggest change for Kotlin devs is that Request and Response are now Kotlin.
Feedback/criticism is welcome!
Show HN: Javalin REST Library – Rewritten in Kotlin
I'm not really trying to convince devs whose main language is Kotlin to use Javalin, it's made more for Java devs and Java devs who are looking to switch to Kotlin.
That being said..! Ktor Hello World example isn't very pretty, and I can't find the docs. All I found was a mostly empty wiki. Where are the official docs?
By the way, pull-requests for other embedded servers would be very welcome in Javalin.
Javalin has no static API, and no concept of "Routes and Filters". In spark Routes have a return value, in Javalin you just have "Handlers" which operate on the request and response. Javalin can do automatic object-mapping to and from json, and has lifecycle events.
Javalin has a built in mechanism for auth (AccessManager)
Javalin has no WebSocket support, and doesn't do static file handling (it leaves this to the embedded server). Javalin runs before-handlers before static files, Spark does not.
Javalin has a fluent api.
Javalin is implemented as a servlet, not a filter.
After-handlers are run after everything (even in case of exceptions), (Spark has after-after filters).
There are many more small differences. I'm one of the maintainers of Sparkjava. Javalin is the result of using Spark daily for the past two years, fixing minor annoyances and including new concepts I would find myself implementing over and over again.