Code: gitlab.com/har... In this video I have compared the performance of Springboot Web MVC application vs Springboot Webflux app. The app is written in Kotlin
Excellent video. Congratulations! I would like to see in more detail each connection between the components within the application, but anyway this video is a great introduction, very complete.
Hi There, I have not run the test but I am confident that Virtual threads will not gain same level of performance as Webflux the reasons being. 1. Virtual threads also block the operations when IO operations are helping 2. Virtual threads use OS threads under the hood which effectively means that they will be limited again. The performance benefit is mainly gained by doing a non blocking nature of Webflux. A good analogy I saw in one of the youtube video is, think of situation where you go to a restaurant. Lets say there are two types of restaurants one of them provided you dedicated waiter who will be assigned to you when you go to eat and will stay with you 100% for the whole duration you are there standing by your desk. The other type is our regular restaurant where a waiter will take your request and while you are eating will attend other customers. In the first example restaurant can only have as many tables as the waiters but in the later example say one waiter is able to attend 10 tables so the restaurant can have 10x tables than the number of waiters. Hope that helps. Thanks.
Excellent video. Congratulations!
I would like to see in more detail each connection between the components within the application, but anyway this video is a great introduction, very complete.
Very well explained, this video should be trending……
Thanks for your kind words 🙏
With Virtual Threads in Java 21 , can we run same tests. Does Web provide same results as webflux..
Hi There, I have not run the test but I am confident that Virtual threads will not gain same level of performance as Webflux the reasons being.
1. Virtual threads also block the operations when IO operations are helping
2. Virtual threads use OS threads under the hood which effectively means that they will be limited again.
The performance benefit is mainly gained by doing a non blocking nature of Webflux. A good analogy I saw in one of the youtube video is, think of situation where you go to a restaurant. Lets say there are two types of restaurants one of them provided you dedicated waiter who will be assigned to you when you go to eat and will stay with you 100% for the whole duration you are there standing by your desk. The other type is our regular restaurant where a waiter will take your request and while you are eating will attend other customers. In the first example restaurant can only have as many tables as the waiters but in the later example say one waiter is able to attend 10 tables so the restaurant can have 10x tables than the number of waiters. Hope that helps. Thanks.