Now, would you say, <@U0BUH9FRD>, that Spring Fu i...

# server

[orangy]

Now, would you say, @sdeleuze, that Spring Fu is inspired by #ktor?

[napperley]

Spring Fu might even be inspired by #vertx.

[nfrankel]

Vert.x was started by Tim Fox in 2011 while he was employed by VMware.

[nfrankel]

Spring Framework was written by Rod Johnson, who released the framework with the publication of his book Expert One-on-One J2EE Design and Development in October 2002

[sdeleuze]

Believe me or not, I never had a look to Ktor to avoid tentation to copy.

[sdeleuze]

Most of Spring Fu was announce in https://spring.io/blog/2017/08/01/spring-framework-5-kotlin-apis-the-functional-way

[sdeleuze]

And https://github.com/tgirard12/spring-webflux-kotlin-dsl

[nfrankel]

i don’t see anything in the documentation regarding integration with regular spring beans
did i miss something?
or does that mean that it’s all or nothing?
it could ease migration a lot if there would be some integration path

[orangy]

@sdeleuze I see, may be you should look at ktor, there’s no problem copying, and may be you can find some ideas for better DSLs

[sdeleuze]

@nfrankel These are regular Spring beans. You can mix JavaConfig and functional beans if you use the right application context impl. Please create a documentation issue about that I will update the doc.

[sdeleuze]

@orangy Sure I will have a look

[nfrankel]

@sdeleuze i’m thinking about migrating the spring pet clinic

[sdeleuze]

Good idea, maybe when SQL support will be available

[nfrankel]

and when it’s available as a standard dep 😉

[orangy]

Is the underlying implementation still the same? I’m wondering, because in TechEmpower Benchmarks Spring is somewhere at the bottom, and I wonder why. And if Spring Fu will have a different story.

[sdeleuze]

1) TechEmpower benchmark, especially the simple tests are very far from real world use cases so not really relevant. 2) Spring Fu is based on WebFlux.fn which is I believe not benchmarked yet, but Reactor and Netty super fast and scalable and WebFlux.fn is a very thin layer on top of that so I am confident 3) Spring Fu and WebFlux targets much more than just request / Reponse.

We will give the SQL benchmark a try asap Reactive SQL support is finished.

[nfrankel]

i’d really be in a favor of a non-webflux implementation
i’m afraid a lot of people already think about migrating to webflux
while reactive is clearly not suited to every use-case

[sdeleuze]

I would agree with Reactive API only but one of the Spring Fu design principle is to provide Coroutines API as well for imperative-like programming.

[sdeleuze]

So along with Reactive + Coroutines SQL support, no need for this double web engine story.