Hey there :wave: Is there any solution by now to f...

# ktor

[Marc Knaup]

Hey there 👋
Is there any solution by now to forward certain vert.x requests to Ktor?
So that Ktor re-uses vert.x’ HTTP server and handles only certain routes.

[Big Chungus]

have ktor routes under different port and proxy vert.x requests to <http://localhost>:<KTOR_PORT>/<path>?

[Marc Knaup]

That’s my backup plan in case there’s no good solution 😅

Sounds nasty, esp. with websockets involved.

[Big Chungus]

It IS nasty!

[Big Chungus]

Alternatively you could reuse the same services from both, ktor and vert.x

[Marc Knaup]

I can only use one HTTP port

[Robert Jaros]

Why do you need to use both?

[Marc Knaup]

I have a larger vert.x Java project that is to be migrated to Kotlin + Ktor over time.
So migrated code would use Ktor route while old code would use vert.x route.

[Robert Jaros]

What advantages gives Ktor vs Vert.x with Kotlin?

[Marc Knaup]

We’re familiar with it.

[kenkyee]

Why not migrate to Quarkus?

[Big Chungus]

You could just as well ask "why not migrate to micronout". All of them are good in their own way. In the end it boils down to preference and familiarity...

[Marc Knaup]

Yup. Back on topic please 😄

[Robert Jaros]

You could check the sources of micronaut-ktor module, which embeds Ktor inside Micronaut, reusing Micronaut's native http server.
https://github.com/micronaut-projects/micronaut-kotlin/tree/master/ktor/src/main/kotlin/io/micronaut/ktor

[Robert Jaros]

Here is the guide of the module: https://micronaut-projects.github.io/micronaut-kotlin/latest/guide/

[Marc Knaup]

That replaces the existing HTTP server with Ktor instead of just adding Ktor as 2nd level

[kenkyee]

Quarkus is vert.x underneath which is why I suggested it...

[kenkyee]

At any rate, doing a proxy is probably simplest but I'd suggest rewriting the websocket piece...