Hello! From what I’ve seen, ktor has been steadily...

# ktor

[evkaky]

Hello!
From what I’ve seen, ktor has been steadily moving beyond being an HTTP-only framework over the past few years. Official WebRTC and gRPC support landed recently, and that’s really great!
But I’m curious if the team is considering some other big features:

1. Official GraphQL support - both server and client.
2. Official support for popular queue/streaming engines. There are more and more Kafka-compatible streaming engines on the market, and Kafka’s wire protocol is becoming something of a standard. So having official Kafka support would be a nice start.
3. Integration with serverless platforms. This one is probably tricky, as it would require close collaboration with the serverless teams at AWS/Azure/GCP/Cloudflare. But being able to reuse the same HTTP/gRPC/GraphQL/Kafka handlers both on-prem and in serverless environments, with minimal changes, would be a big win.
Is there anyone from the team who could comment on this?
The last ktor roadmap was published a year ago, so it’s not really clear to the community how the team plans to evolve Ktor in the near future

[Oliver.O]

The latest Kotlin roadmap contains an Ecosystem section with Ktor items.

[Alexander Sysoev]

Hi @evkaky!
Thank you for your question, and let me give a brief update in general and for your questions in particular.
Ktor currently has its primary focus on building the ecosystem, providing key integrations, and improving existing features. In some examples:
• New observability APIs and improved integrations
• Improved authentication and new authorization
• Healthcheck for existing subsystems, meaning we revisit some of Ktor's components and try to fix systematic problems
• Onboarding and comprehensive tutorials that show production-ready apps with Ktor
In general, you can say that the near future is about making Ktor work flawlessly in the scenarios where it is already used and closing some existing gaps, such as observability and authorization.

For your questions in particular:
• For GraphQL, we currently expect people to use community integrations
• We don't have any plans that we can share right now about Kafka, but we consider it to be an important integration for Ktor
• Serverless is not considered a priority right now, but some changes that we do now will also help us support serverless in the future, if we decide to do so
We'll post a detailed roadmap in the following months

[mbonnin]

Shameless plug for my GraphQL - Ktor integration: apollographql.github.io/apollo-kotlin-execution/ktor.html#…