Battle Of The Microservice Frameworks: Micronaut versus Quarkus edition! by Michel Schudel
Вставка
- Опубліковано 3 лис 2019
- Micronaut and Quarkus are two cool emerging Java backend frameworks that aim to solve some problems that exist in current frameworks, like faster startup, low memory footprint, and support for ahead-of-time compilation using GraalVM. In this session, we'll square off both frameworks against each other.
How do they compare, what are the stronger and weaker points of both frameworks?
We'll compare the following features:
Initializing your project
Building your first restcontroller / programming model
Startup time
Database support
Integration test support
Building native images
Memory usage and JAR sizes
Ease of cloud deployment
In the end, we might have a clear winner! ... or will we?
Michel Schudel has been a passionate Java developer since 1998, building various Java solutions for banks, insurance companies and telecom providers. Since then he has seen the good, the bad and the ugly in Java land. He loves agile development and coding with frameworks like SpringBoot to get up-and-running as fast as possible. Futhermore, he likes to coach junior developers in Core Java. Michel is currently working for Rabobank in the Netherlands. - Наука та технологія
On 11:00 its about the configuration file. Since December yaml is also supported on Quarkus. (video was recorded before)
Ha! Opening a bunch of videos of things that look interesting and then who do I see? only Michel from two desks over. When everyone said "ohh Michel's not here this week, he's at Devoxx" I didn't realise you'd be speaking.
Quarkus is better if it is your first framework or you're seriously worried about memory.
Micronaut is better if you already know Spring because it so similar and preformed better.
Micronaut is more matured than Quarkus.
But i think Quarkus will win in long run.
wise words imo
Thanks for the great comparison. Really appreciate it!
Great comparison, a little biased for micronaut, but great :)
also Quarkus supports Spring. If you like Spring with Quarkus you can simply use Spring...
Good work, I like quarkus
for the impatient 28:15
Nice comparisons
“Quarkonaut”
Correct me, but important additions - Quarkus - has hot reload out of the box. Very good for rapid development. Micronaut has better kotlin suport.
@@luisdanielmesa How it is working for you? Which framework?
We've gone through this process and are using Micronaut. Grails 4 (i think) is now underpinned by Micronaut instead of Spring Boot. Spring data was ported from GORM in 2011 for Java devs. The same devs responsible for GORM did Micronaut Data. MongoDB is incoming soon I think.
I noticed both of them inspired by Spring, should we think about leaving Spring then?
The framework experience is similar to that of spring. But what they try to achieve and how they do it is very different.
I’ve been using Spring since 2006, and i’d say Spring is still king. But once you’ve tried Micronuat or Quarkus and experience how fast they are, Spring suddenly feels really ancient. I had about 400+ integration tests in my micronaut project before. It executes in my mac air in 5 minutes.
@@luisdanielmesa not sure where the difference is. Sounds like we have the same experience 😅
It's 2023 here and my vote goes for Quarkus.
Why is this person starting micronaut 2nd and comparing time ?! Quarqus had more ram/cpu at startup!
Visit www.microstarter.io to bootstrap Micronaut Applications
Micronaut wins.
What lead to think you so?
....Developer WINS!!!!!!