@Rob Elliot I'm curious as to what you're after. Is it that you want to see something on a larger scale, something with all types of testing? The "use case" for any application isn't the choice of library - any web library will do JSON on a Rest API! Are you looking to choose a kotlin-based backend - in which case I'd recommend doing a few spikes in various things and choosing what you like the most! I'd recommend avoid going all in on anything until you're sure you can reverse out if it goes wrong. And beware any library which has such a lockin from the start. If you do something like hexagonal architecture, you should be able to switch out the web layer with not too much effort. 🙂
If you'll allow me to do a bit of a sales job.. 😉
When we work with companies to implement platforms on top of http4k, the reasons that they have chosen it are because of the developer experience, the portability of the code (run it the same in-memory, on a server, on serverless, in graal), the amount of integrations, the simplicity and the strong focus on testing. This last one is very important to us and is why the project has such a strong focus on that in particular.
</end>