Interesting presentation, now I am sure that Micronaut has no added value over SpringBoot we use everyday for 10 years. Nowadays new frameworks should show breakthrough features and not just a slight rework of the existing framework to get adoption by the dev community. The most important thing in projects right now is to stick with the existing technologies that everyone in the team already master so that we can face the huge challenges ahead of us.
18:10 You are having micronaut-http-server-netty but are using H2 database that is not reactive. I think that maybe better option was to use other database (for example r2dbc-h2). I guess that on 37:25 that number of threads are not default (2*number of cores) - in netty. I think that this was caused by not using reactive database. For tests performance i would recommend using sth like Gatling.
th-cam.com/video/utfX9jZmv2A/w-d-xo.html You are using H2 database which is bad choice for comparing when using netty (and in the same pom I see you are using micronaut-http-server-netty). We can see on: th-cam.com/video/utfX9jZmv2A/w-d-xo.html that number of threads is different than default netty application. Better option is to use reactive database for example: r2dbc-h2 and then compare it with Spring application that also uses netty.
Is your car running on a steam engine and wooden wheel? Because, you see, those came before fuel propelled engins and rubber tires. Yet, if it's bad to re-invent the same thing, why do nobody use the first made wheels and motors? Similarly, Spring Boot doesn't run in Graalvm (for now) and uses a lot reflexions. It's technology evolution.
@@gokudomatic What Micronaut initially brought to the table was compile-time dependency injection and GraalVM support. One could argue there was no strict need to write a Spring framework clone on top of that. I appreciate the work they've done, but I also detect traces of the not-invented-here syndrome.
![[LIVE] : ONE ลุมพินี 89 วันนี้!! คู่เอก "ยอดไอคิว vs คิริลล์"](http://i.ytimg.com/vi/Z3vYkHJ_5Ig/mqdefault.jpg)
Interesting presentation, now I am sure that Micronaut has no added value over SpringBoot we use everyday for 10 years. Nowadays new frameworks should show breakthrough features and not just a slight rework of the existing framework to get adoption by the dev community. The most important thing in projects right now is to stick with the existing technologies that everyone in the team already master so that we can face the huge challenges ahead of us.
18:10 You are having micronaut-http-server-netty but are using H2 database that is not reactive. I think that maybe better option was to use other database (for example r2dbc-h2). I guess that on 37:25 that number of threads are not default (2*number of cores) - in netty. I think that this was caused by not using reactive database. For tests performance i would recommend using sth like Gatling.
What about all those @Singleton tags?
th-cam.com/video/utfX9jZmv2A/w-d-xo.html You are using H2 database which is bad choice for comparing when using netty (and in the same pom I see you are using micronaut-http-server-netty).
We can see on: th-cam.com/video/utfX9jZmv2A/w-d-xo.html
that number of threads is different than default netty application.
Better option is to use reactive database for example: r2dbc-h2
and then compare it with Spring application that also uses netty.
just seen this today, it seems like the equivalent of start.spring.io for micronaut www.microstarter.io/
one more framework, good idea to re-invent again same thing...
Is your car running on a steam engine and wooden wheel? Because, you see, those came before fuel propelled engins and rubber tires. Yet, if it's bad to re-invent the same thing, why do nobody use the first made wheels and motors?
Similarly, Spring Boot doesn't run in Graalvm (for now) and uses a lot reflexions. It's technology evolution.
@@gokudomatic What Micronaut initially brought to the table was compile-time dependency injection and GraalVM support. One could argue there was no strict need to write a Spring framework clone on top of that. I appreciate the work they've done, but I also detect traces of the not-invented-here syndrome.