News for hackers. Stuff that matters.

A comment on Learning Spring with Kotlin – Sprint 0. Parent comment

Re:Learning Spring with Kotlin – Sprint 0 by shock on Tuesday April 14, 2020 @06:00PM (#22872033)
Why do you want db access to be non-blocking? Are you not interested in the result?
[ Parent | on HN ]
Re:Learning Spring with Kotlin – Sprint 0 by erik_seaberg on Tuesday April 14, 2020 @06:13PM (#22872138)
I want to resume business logic when the result is available, but I don't want tens of thousands of kernel threads blocked on results until java finally gets fibers. People who write synchronous drivers also tend to make big poorly-used connection pools which defeat TCP flow control.
[ Parent | on HN ]
Re:Learning Spring with Kotlin – Sprint 0 by shock on Tuesday April 14, 2020 @06:33PM (#22872304)
> I don't want tens of thousands of kernel threads blocked on results

If that is because of the memory consumption of kernel threads, be aware you are trading less memory consumption for increased cognitive complexity (if you agree that asynchronicity is more complex than synchronicity).

[ Parent | on HN ]
Re:Learning Spring with Kotlin – Sprint 0 by erik_seaberg on Tuesday April 14, 2020 @08:23PM (#22873062)
True, if hardware cost nothing we might still be on python. Chaining futures with f1.thenApply(arg -> f2) hasn't been that bad, but kotlin's coroutine DSL does look better.
[ Parent | on HN ]