Earlier quoted context omitted.
Strictly imo, using Kotlin with Spring Boot defeats the purpose if you're trying to get away from traditional Java web frameworks (didn't think I needed to spell this out due to the next sentence, but HN gonna HN). Kotlin is a chance to get away from the cruft and annotation magic of traditional Java. I use Ktor and it's everything you need for a modern API (and can be deployed as a WAR if that's why you want Spring…
It depends on your needs I guess. Not all API can be handled by just a few classes. If your plan is to maake a microservice that expose a single value, yes spring boot is likely overkill. But when you have complex models with runtime configuration and profiles and so on... Maybe we need to specify what we are really talking about when we say API. For some it just means a partial implementation of REST.
How does using Ktor preclude one from using anything you just described?
Lol just using Koin alone would bring every thing you just described, with the added benefit of not delving into XML files.
Really some people are just married to the mentality of "If it's not on the feature list, I guess you can't do it". I believe in using focused tools that excel at specific things. Ktor lets you do that.