The ROI of Quarkus for Spring Boot Applications

Quarkus applications are quick to code, start fast, and require much less hardware than their Spring Boot equivalents. They use less memory, less electricity, and handle much higher load. They make both developers and LLMs more productive, saving both time and tokens. So can we quantify the financial benefits of switching from Spring Boot to Quarkus? Yes. (Spoiler – it’s good!) In this talk, Holly will explain the architectural choices which make Quarkus fast. She’ll explain how to choose between JVM and native run modes, depending what kind of “fast” you need. Finally, she’ll demonstrate options for getting from Spring to Quarkus quickly and cheaply, for a near-immediate return on investment.

Transcript

1. Sanil Nambiar Session APD23 | June 2nd, 2026 Holly Cummins, STSM, Quarkus The ROI of Quarkus for Spring Boot Applications
2. Agenda -What is Quarkus? -Why Quarkus? -Can we quantify that? -The developer experience ROI -Getting to Quarkus from Spring Boot
3. @holly_cummins #Quarkus 2022
4. @holly_cummins #Quarkus “I can’t bring up the microservices in my Java dev stack 2022
5. @holly_cummins #Quarkus “I can’t bring up the microservices in my Java dev stack … on my brand new Apple laptop with a M1 chip and - fi ntech CTO 2022
6. @holly_cummins most java web frameworks are resource-hungry they hog cpu and ram
7. @holly_cummins most java web frameworks are verbose there is a lot of typing
8. @holly_cummins #Quarkus in production, it’s worse
9. @holly_cummins #Quarkus in production, it’s worse
10. @holly_cummins #Quarkus in production, it’s worse example microservices maths:
11. @holly_cummins #Quarkus in production, it’s worse example microservices maths: Lufthansa maintenance scheduling system
12. @holly_cummins #Quarkus in production, it’s worse example microservices maths: Lufthansa maintenance scheduling system single service: ½ core + 1 GB RAM
13. @holly_cummins #Quarkus in production, it’s worse example microservices maths: Lufthansa maintenance scheduling system single service: ½ core + 1 GB RAM HA → 3x instances
14. @holly_cummins #Quarkus in production, it’s worse example microservices maths: Lufthansa maintenance scheduling system single service: ½ core + 1 GB RAM HA → 3x instances ~100 microservices
15. @holly_cummins #Quarkus in production, it’s worse example microservices maths: Lufthansa maintenance scheduling system single service: ½ core + 1 GB RAM HA → 3x instances ~100 microservices = 150 cores + 300 GB RAM
16. @holly_cummins #Quarkus why is this happening? mismatch between what we need and what the platform is optimised for
17. enter … quarkus
18. a Java framework that gets you going faster, faster. enter … quarkus
19. what is quarkus?
22. hibernate
23. hibernate rest
24. hibernate rest jackson
25. hibernate rest jackson
26. hibernate netty rest jackson
27. hibernate netty rest langchain4j jackson
28. hibernate netty rest langchain4j jackson etc
29. hibernate netty rest langchain4j jackson etc
30. hibernate netty rest langchain4j jackson etc
31. hibernate netty rest langchain4j jackson etc runtime infrastructure
32. hibernate netty rest langchain4j jackson etc runtime infrastructure build infrastructure
33. hibernate netty rest langchain4j jackson etc runtime infrastructure build infrastructure
34. hibernate netty rest langchain4j jackson etc runtime infrastructure build infrastructure
35. hibernate netty rest langchain4j jackson etc runtime infrastructure build infrastructure
36. hibernate netty rest langchain4j jackson etc runtime infrastructure build infrastructure
37. hibernate netty rest langchain4j jackson etc runtime infrastructure build infrastructure
38. hibernate netty rest langchain4j jackson etc runtime infrastructure build infrastructure
39. hibernate netty rest langchain4j jackson etc runtime infrastructure build infrastructure
40. hibernate netty rest langchain4j jackson etc runtime infrastructure build infrastructure
41. netty etc runtime infrastructure build infrastructure hibernate rest langchain4j jackson - An integrated collection of your favourite libraries (Hibernate, Jackson, dependency injection, Netty, etc) - A super-scalable core, build on Eclipse Vert.x - Minimises unnecessary work at runtime
42. netty etc runtime infrastructure build infrastructure hibernate rest langchain4j jackson - An integrated collection of your favourite libraries (Hibernate, Jackson, dependency injection, Netty, etc) - A super-scalable core, build on Eclipse Vert.x - Minimises unnecessary work at runtime
45. e ffi ciency
46. e ffi ciency build-time principle
47. e ffi ciency build-time principle reactive core
48. e ffi ciency developer experience (also e ffi ciency) build-time principle reactive core
49. e ffi ciency developer experience (also e ffi ciency) build-time principle reactive core live reload
50. e ffi ciency developer experience (also e ffi ciency) build-time principle reactive core live reload continuous testing
51. e ffi ciency developer experience (also e ffi ciency) build-time principle reactive core minimising boilerplate live reload continuous testing
52. e ffi ciency developer experience (also e ffi ciency) build-time principle reactive core minimising boilerplate live reload continuous testing dev ui
53. e ffi ciency developer experience (also e ffi ciency) build-time principle reactive core minimising boilerplate live reload continuous testing dev ui
54. e ffi ciency developer experience (also e ffi ciency) build-time principle reactive core minimising boilerplate live reload continuous testing dev ui
55. why is quarkus novel?
56. @holly_cummins application frameworks were optimised for dynamism
57. @holly_cummins application frameworks optimised for dynamism dynamism has a cost
58. @holly_cummins paying a dynamism tax … even though the app is not dynamic
59. @holly_cummins a highly dynamic runtime in a container is pointless
60. @holly_cummins #RedHat most apps are immutable now
61. @holly_cummins #RedHat most apps are immutable now
62. @holly_cummins #RedHat most apps are immutable now
63. @holly_cummins #RedHat most apps are immutable now
64. @holly_cummins #RedHat most apps are immutable now
65. @holly_cummins #RedHat most apps are immutable now
66. @holly_cummins #Quarkus how does a java framework start?
67. @holly_cummins #Quarkus how does a java framework start? build time
68. @holly_cummins #Quarkus how does a java framework start? build time runtime
69. @holly_cummins #Quarkus how does a java framework start? build time runtime
70. @holly_cummins #Quarkus how does a java framework start? packaging (maven, gradle…) build time runtime
71. @holly_cummins #Quarkus how does a java framework start? build time runtime
72. @holly_cummins #Quarkus how does a java framework start? build time runtime
73. @holly_cummins #Quarkus how does a java framework start? </> build time runtime load and parse • config files • properties • yaml • xml • etc.
74. @holly_cummins #Quarkus how does a java framework start? </> build time runtime
75. @holly_cummins #Quarkus how does a java framework start? @ @ </> build time runtime • classpath scanning and annotation discovery • attempt to load class to enable/disable features
76. @holly_cummins #Quarkus how does a java framework start? @ @ </> build time runtime
77. @holly_cummins #Quarkus how does a java framework start? @ @ </> build time runtime build a metamodel of the world
78. @holly_cummins #Quarkus how does a java framework start? @ @ </> build time runtime
79. @holly_cummins #Quarkus how does a java framework start? @ @ </> build time runtime start • thread pools • I/O • etc.
80. @holly_cummins #Quarkus how does a java framework start? @ @ </> build time runtime ready to do work!
81. @holly_cummins #Quarkus what if we start the application more than once? @ @ </>
82. @holly_cummins #Quarkus what if we start the application more than once? @ @ </> @ @ </>
83. @holly_cummins #Quarkus what if we start the application more than once? @ @ </> @ @ </> @ @ </>
84. @holly_cummins #Quarkus what if we start the application more than once? @ @ </> @ @ </> @ @ </> @ @ </>
85. @holly_cummins #Quarkus what if we start the application more than once? @ @ </> @ @ </> @ @ </> @ @ </>
86. @holly_cummins #Quarkus what if we start the application more than once? @ @ </> @ @ </> @ @ </> @ @ </> so much work gets redone every time
87. @holly_cummins Hibernate speed example: JTA auto-wiring
88. @holly_cummins Hibernate speed example: JTA auto-wiring Class.forName(“LikelyJTAImplementation”);
89. @holly_cummins Hibernate speed example: JTA auto-wiring Class.forName(“LikelyJTAImplementation”);
90. @holly_cummins Hibernate speed example: JTA auto-wiring Class.forName(“LikelyJTAImplementation”); Class.forName(“APossibleJTAImplementation”);
91. @holly_cummins Hibernate speed example: JTA auto-wiring Class.forName(“LikelyJTAImplementation”); Class.forName(“APossibleJTAImplementation”); Class.forName(“AnotherJTAImplementation”);
92. @holly_cummins Hibernate speed example: JTA auto-wiring Class.forName(“LikelyJTAImplementation”); Class.forName(“APossibleJTAImplementation”); Class.forName(“AnotherJTAImplementation”); …
93. @holly_cummins Hibernate speed example: JTA auto-wiring Class.forName(“LikelyJTAImplementation”); Class.forName(“APossibleJTAImplementation”); Class.forName(“AnotherJTAImplementation”); Class.forName(“NicheJTAImplementation”); …
94. @holly_cummins Hibernate speed example: JTA auto-wiring Class.forName(“LikelyJTAImplementation”); Class.forName(“APossibleJTAImplementation”); Class.forName(“AnotherJTAImplementation”); Class.forName(“NicheJTAImplementation”); Class.forName(“VeryNicheJTAImplementation”); …
95. @holly_cummins Hibernate speed example: JTA auto-wiring Class.forName(“LikelyJTAImplementation”); Class.forName(“APossibleJTAImplementation”); Class.forName(“AnotherJTAImplementation”); Class.forName(“NicheJTAImplementation”); Class.forName(“VeryNicheJTAImplementation”); …
96. @holly_cummins Hibernate speed example: JTA auto-wiring Class.forName(“LikelyJTAImplementation”); Class.forName(“APossibleJTAImplementation”); Class.forName(“AnotherJTAImplementation”); Class.forName(“NicheJTAImplementation”); Class.forName(“VeryNicheJTAImplementation”); … ~129 auto-wiring attempts
97. @holly_cummins Hibernate speed example: JTA auto-wiring Class.forName(“LikelyJTAImplementation”); Class.forName(“APossibleJTAImplementation”); Class.forName(“AnotherJTAImplementation”); Class.forName(“NicheJTAImplementation”); Class.forName(“VeryNicheJTAImplementation”); … ~129 auto-wiring attempts every single start.
98. @holly_cummins it’s not just JTA this happens for lots of internal service bindings
99. @holly_cummins JVM footprint example: Hibernate
100. @holly_cummins JVM spends time loading classes for specific databases JVM class for unused database class for unused database class for unused database class for unused database class for unused database class for unused database class for unused database class for unused database class for unused database class for unused database class for unused database class for unused database class for unused database class for unused database class for unused database class for unused database footprint example: Hibernate
101. @holly_cummins JVM spends time loading classes for specific databases JVM class for unused database class for unused database class for unused database class for unused database class for unused database class for unused database class for unused database class for unused database class for unused database class for unused database class for unused database class for unused database class for unused database class for unused database class for unused database class for unused database turns out they’re never used footprint example: Hibernate
102. @holly_cummins JVM spends time loading classes for specific databases JVM turns out they’re never used JIT spends time unloading classes footprint example: Hibernate
103. @holly_cummins Hibernate example: ~500 classes which are only useful if you're running an Oracle database loaded and then unloaded
104. @holly_cummins Hibernate example: ~500 classes which are only useful if you're running an Oracle database loaded and then unloaded every single start.
105. @holly_cummins the true cost of loaded classes isn’t just memory + start time
106. @holly_cummins the true cost of loaded classes isn’t just memory + start time method dispatching:
107. @holly_cummins interface the true cost of loaded classes isn’t just memory + start time method dispatching:
108. @holly_cummins unused implementation the one we want interface unused implementation unused implementation the true cost of loaded classes isn’t just memory + start time method dispatching:
109. @holly_cummins unused implementation the one we want interface unused implementation unused implementation the true cost of loaded classes isn’t just memory + start time method dispatching:
110. @holly_cummins unused implementation the one we want interface megamorphic call slow dispatching unused implementation unused implementation the true cost of loaded classes isn’t just memory + start time method dispatching:
111. @holly_cummins the true cost of loaded classes isn’t just memory + start time the one we want interface
112. @holly_cummins the true cost of loaded classes isn’t just memory + start time the one we want monomorphic call fast dispatching interface
113. @holly_cummins how do we fix all this?
114. @holly_cummins #Quarkus @ @ </> build time runtime what if we initialize at build time?
115. @holly_cummins #Quarkus @ @ </> build time runtime what if we initialize at build time?
116. @holly_cummins #Quarkus @ @ </> build time runtime start • thread pools • I/O • etc. what if we initialize at build time?
117. @holly_cummins #Quarkus @ @ </> build time runtime ready to do work! start • thread pools • I/O • etc. what if we initialize at build time?
118. @holly_cummins #Quarkus @ @ </> repeated starts are now efficient
119. @holly_cummins #Quarkus @ @ </> repeated starts are now efficient
120. @holly_cummins #Quarkus @ @ </> repeated starts are now efficient
121. @holly_cummins #Quarkus @ @ </> repeated starts are now efficient
122. @holly_cummins #Quarkus @ @ </> repeated starts are now efficient
123. @holly_cummins #Quarkus @ @ </> repeated starts are now efficient
124. @holly_cummins #Quarkus @ @ </> repeated starts are now efficient less wasted work
125. @holly_cummins #Quarkus the Quarkus way enables native compilation native (graalvm) @ @ </> jvm build time
126. @holly_cummins #Quarkus the Quarkus way enables native compilation native (graalvm) @ @ </> jvm build time
127. to the code! native binaries with Quarkus
128. #Quarkus @holly_cummins 2020
129. #Quarkus @holly_cummins hey, wanna see quarkus? hey, wanna see quarkus? hey, wanna see quarkus? hey, wanna see quarkus? hey, wanna see quarkus? 2020
130. #Quarkus @holly_cummins hey, wanna see quarkus? hey, wanna see quarkus? hey, wanna see quarkus? hey, wanna see quarkus? hey, wanna see quarkus? uhh … are you supposed to shut down applications after using them? 2020
131. #Quarkus @holly_cummins hey, wanna see quarkus? hey, wanna see quarkus? hey, wanna see quarkus? hey, wanna see quarkus? hey, wanna see quarkus? uhh … are you supposed to shut down applications after using them? 120 instances (!) 2020
132. @holly_cummins
133. @holly_cummins doing more up-front
134. @holly_cummins doing more up-front - speeds up start
135. @holly_cummins doing more up-front - speeds up start - shrinks memory footprint
136. @holly_cummins doing more up-front - speeds up start - shrinks memory footprint - improves throughput (!)
137. can we quantify that?
138. spoiler:
139. 2 - 3x infra savings spoiler:
140. to the code! performance comparisons
141. https://github.com/quarkusio/spring-quarkus-perf-comparison
142. quarkus has great performance
143. quarkus starts fast
144. quarkus is lean with memory
145. quarkus has super throughput
146. how does all that impact costs?
147. low load pack many instances onto a node memory is the limiting factor how much hardware does an app need? high load horizontally scale to support load max throughput is the limiting factor
148. machine (1GiB RAM)
149. machine (1GiB RAM) 300 MiB RAM
150. machine (1GiB RAM) 300 MiB RAM 300 MiB RAM
151. machine (1GiB RAM) 300 MiB RAM 300 MiB RAM 300 MiB RAM
152. machine (1GiB RAM) 300 MiB RAM 300 MiB RAM 300 MiB RAM 300 MiB RAM
153. machine (1GiB RAM) 300 MiB RAM 300 MiB RAM 300 MiB RAM
155. assumptions: EC2 c6i.xlarge instance, us-east-1, $0.17 per hour low load scenario: cost per instance per year
156. quarkus spring p r i 0.17 p r i 1489.2 assumptions: EC2 c6i.xlarge instance, us-east-1, $0.17 per hour low load scenario: cost per instance per year
157. quarkus spring p r i 0.17 p r i 1489.2 jvm US$64.75 US$135.38 assumptions: EC2 c6i.xlarge instance, us-east-1, $0.17 per hour low load scenario: cost per instance per year
158. quarkus spring p r i 0.17 p r i 1489.2 jvm US$64.75 US$135.38 native US$19.86 US$64.75 assumptions: EC2 c6i.xlarge instance, us-east-1, $0.17 per hour low load scenario: cost per instance per year
159. quarkus spring p r i 0.17 p r i 1489.2 jvm US$64.75 US$135.38 native US$19.86 US$64.75 assumptions: EC2 c6i.xlarge instance, us-east-1, $0.17 per hour low load scenario: cost per instance per year 2.1x
160. quarkus spring p r i 0.17 p r i 1489.2 jvm US$64.75 US$135.38 native US$19.86 US$64.75 assumptions: EC2 c6i.xlarge instance, us-east-1, $0.17 per hour low load scenario: cost per instance per year 2.1x 3.3x
161. p r i p r i jvm native quarkus 0.17 1489.2 US$6,475 US$1,986 spring US$13,538 US$6,475 low load scenario: cost per hundred instances per year assumptions: EC2 c6i.xlarge instance, us-east-1, $0.17 per hour
162. 10,000 tps
163. 10,000 tps machine 15,000 tps
164. 10,000 tps 20,000 tps machine 15,000 tps
165. 10,000 tps 20,000 tps machine 15,000 tps machine 15,000 tps machine 15,000 tps
166. 10,000 tps 20,000 tps 30,000 tps machine 15,000 tps machine 15,000 tps machine 15,000 tps
167. 10,000 tps 20,000 tps 30,000 tps machine 15,000 tps machine 15,000 tps machine 15,000 tps machine 15,000 tps machine 15,000 tps
168. 10,000 tps 20,000 tps 30,000 tps 40,000 tps machine 15,000 tps machine 15,000 tps machine 15,000 tps machine 15,000 tps machine 15,000 tps
169. 10,000 tps 20,000 tps 30,000 tps 40,000 tps machine 15,000 tps machine 15,000 tps machine 15,000 tps machine 15,000 tps machine 15,000 tps machine 15,000 tps machine 15,000 tps machine 15,000 tps
171. native 2.5x
172. jvm 1.7x native 2.5x
174. native $85k savings/year
175. jvm $16k savings/year native $85k savings/year
176. low load quarkus native uses ⅓ the memory of spring native how much can quarkus save you? high load quarkus on jvm can handle 1.7x more requests than spring boot
177. #Quarkus @holly_cummins we also see better response times
178. #Quarkus @holly_cummins users care (a lot) about response time we also see better response times
179. can we trust this data?
180. what we see in the fi eld matches what we see in the lab.
181. https://www.reddit.com/r/SpringBoot/comments/1tj5tsn/comment/on04x23/
182. https://www.reddit.com/r/SpringBoot/comments/1tj5tsn/comment/on04x23/ 2.7x less memory
183. @holly_cummins #Quarkus remember the airline scheduling application?
184. @holly_cummins #Quarkus remember the airline scheduling application? “[With Quarkus], we can run 3 times denser deployments without sacrificing availability and response times of services. ” – Thorsten Pohl
185. @holly_cummins #Quarkus remember the airline scheduling application? “[With Quarkus], we can run 3 times denser deployments without sacrificing availability and response times of services. ” – Thorsten Pohl 3x less hardware
186. is quarkus greener?
187. @holly_cummins #Quarkus
188. to the code! energy comparisons
189. @holly_cummins #RedHat Setup: • REST + CRUD • large heap • RAPL energy measurement • multiple instances to support high load
 Assumptions: • US energy mix Source: John O’Hara experiment 1: RAPL measurements
190. @holly_cummins #RedHat Setup: • REST + CRUD • large heap • RAPL energy measurement • multiple instances to support high load
 Assumptions: • US energy mix Source: John O’Hara experiment 1: RAPL measurements quarkus on JVM has the lowest carbon … because it has the highest throughput
191. @holly_cummins #RedHat Setup: • REST + CRUD • large heap • RAPL energy measurement • multiple instances to support high load
 Assumptions: • US energy mix Source: John O’Hara experiment 1: RAPL measurements quarkus on JVM has the lowest carbon … because it has the highest throughput ~½ the energy requirements
192. @holly_cummins #RedHat density Source: Clement Esco ff i er experiment 2: cloud Setup: • 800 requests/second, over 20 days • SLA > 99% • AWS instances Assumptions: • Costs are for us-east-1 data centre
193. @holly_cummins #RedHat interpolated carbon metrics – hardware and electricity Setup: • 800 requests/second, over 20 days • SLA > 99% Assumptions: • 50% load Source: Clement Esco ffi er x Teads cloud carbon impact of framework choice
194. @holly_cummins #RedHat interpolated carbon metrics – hardware and electricity Setup: • 800 requests/second, over 20 days • SLA > 99% Assumptions: • 50% load Source: Clement Esco ffi er x Teads cloud carbon impact of framework choice the carbon is lower because the cost is lower
195. @holly_cummins #RedHat interpolated carbon metrics – hardware and electricity Setup: • 800 requests/second, over 20 days • SLA > 99% Assumptions: • 50% load Source: Clement Esco ffi er x Teads cloud carbon impact of framework choice the carbon is lower because the cost is lower ~½ the carbon
196. @holly_cummins #Quarkus ~½ the carbon
197. developer experience
198. developers cost money too
199. @holly_cummins #Quarkus quarkus enables faster feedback
200. @holly_cummins #Quarkus mvn quarkus:dev zero-con fi g live coding
201. @holly_cummins #Quarkus tests are run on every code change “reverse code coverage” means only relevant tests run mvn quarkus:dev continuous testing
202. @holly_cummins #Quarkus developer UI
203. to the code! dev mode and continuous testing
204. @holly_cummins #Quarkus with quarkus, developers have to type less boilerplate
205. @holly_cummins #Quarkus with quarkus, developers have to read less boilerplate
206. @holly_cummins #Quarkus zero-con fi g testcontainers
207. @holly_cummins #Quarkus testcontainers integration … without quarkus @TestConfiguration(proxyBeanMethods = false) public class ContainersConfig { @Bean @ServiceConnection public PostgreSQLContainer<?> postgres() { return new PostgreSQLContainer<>(DockerImageName.parse("postgres:14")); } } public class TestApplication { public static void main(String[] args) { SpringApplication .from(MySpringDataApplication::main) .with(ContainersConfig.class) .run(args); } } @Import(ContainersConfig.class)
208. @holly_cummins #Quarkus testcontainers integration … without quarkus
209. @holly_cummins #Quarkus zero-config testcontainers integration the only thing you need to do to make testcontainers work is not con fi gure anything # configure your datasource quarkus.datasource.db-kind = postgresql quarkus.datasource.username = sarah quarkus.datasource.password = connor quarkus.datasource.jdbc.url = jdbc:postgresql://localhost:5432/mydatabase # drop and create the database at startup quarkus.hibernate-orm.database.generation = drop-and-create
210. @holly_cummins #Quarkus zero-config testcontainers integration the only thing you need to do to make testcontainers work is not con fi gure anything # drop and create the database at startup quarkus.hibernate-orm.database.generation = drop-and-create
211. @holly_cummins #Quarkus zero-config testcontainers integration the only thing you need to do to make testcontainers work is not con fi gure anything
212. @holly_cummins #Quarkus zero-config testcontainers integration the only thing you need to do to make testcontainers work is not con fi gure anything quarkus also auto-invokes fl yway and liquibase
213. @holly_cummins #Quarkus @ApplicationScoped public class GreetingRepository { public Entity findByName(int name) { return find("name", name).firstResult(); } void persist(Entity entity) {} void delete(Entity entity) {} Entity findById(Id id) {} List<Entity> list(String query, Sort sort, Object... params) { return null; } Stream<Entity> stream(String query, Object... params) { return null; } long count() { return 0; } long count(String query, Object... params) { return 0; } } example: panache + hibernate
214. @holly_cummins #Quarkus example: panache + hibernate @ApplicationScoped public class GreetingRepository implements PanacheRepository<Greeting> { public Entity findByName(int name) { return find("name", name).firstResult(); } }
215. @holly_cummins #Quarkus DAO example: panache + hibernate @ApplicationScoped public class GreetingRepository implements PanacheRepository<Greeting> { public Entity findByName(int name) { return find("name", name).firstResult(); } } repository pattern
216. @holly_cummins #Quarkus example: panache + hibernate
217. @holly_cummins #Quarkus example: panache + hibernate active record pattern @Entity public class Greeting extends PanacheEntity { public String name; public LocalDate issued; @Version public int version; public static List<Greeting> getTodaysGreetings() { return list("date", LocalDate.now()); } }
218. @holly_cummins #Quarkus can we quantify that?
219. https://www.reddit.com/r/SpringBoot/comments/1tj5tsn/comment/on04x23/
220. https://www.reddit.com/r/SpringBoot/comments/1tj5tsn/comment/on04x23/ 40% less code
221. Christos Sotiriou, DXL technical lead at Vodafone Greece
222. 2019: Moved digital experience to quarkus (from Spring Boot) Christos Sotiriou, DXL technical lead at Vodafone Greece
223. 2019: Moved digital experience to quarkus (from Spring Boot) • Startup times 40s ➡ 12s Christos Sotiriou, DXL technical lead at Vodafone Greece
224. 2019: Moved digital experience to quarkus (from Spring Boot) • Startup times 40s ➡ 12s • RAM 800 MB ➡ 360 MB Christos Sotiriou, DXL technical lead at Vodafone Greece
225. 2019: Moved digital experience to quarkus (from Spring Boot) • Startup times 40s ➡ 12s • RAM 800 MB ➡ 360 MB • Developer productivity ⬆ 30-40%– Christos Sotiriou, DXL technical lead at Vodafone Greece
226. 2019: Moved digital experience to quarkus (from Spring Boot) • Startup times 40s ➡ 12s • RAM 800 MB ➡ 360 MB • Developer productivity ⬆ 30-40%– 30-40% more productive Christos Sotiriou, DXL technical lead at Vodafone Greece
227. Quarkus Insights #192, https://www.youtube.com/watch?v=YNxz3KaTz5Y
228. Quarkus Insights #192, https://www.youtube.com/watch?v=YNxz3KaTz5Y ~2x more productive
229. Quarkus Insights #192, https://www.youtube.com/watch?v=YNxz3KaTz5Y
230. 2-3x less dev costs Quarkus Insights #192, https://www.youtube.com/watch?v=YNxz3KaTz5Y
231. Quarkus Insights #192, https://www.youtube.com/watch?v=YNxz3KaTz5Y
232. Quarkus Insights #192, https://www.youtube.com/watch?v=YNxz3KaTz5Y
234. “Quarkus is an absolute joy”
235. @holly_cummins job satisfaction is the no. 1 predictor of organizational performance
236. @holly_cummins “Pleasure in the job puts perfection in the work.” Aristotle
237. migration (the i in roi)
238. @holly_cummins #Quarkus
239. @holly_cummins #Quarkus compatibility libraries
240. @holly_cummins #Quarkus <dependency> <groupId>io.quarkus</groupId> <artifactId>quarkus-spring-web</artifactId> </dependency> <dependency> <groupId>io.quarkus</groupId> <artifactId>quarkus-spring-data-jpa</artifactId> </dependency> compatibility libraries
241. @holly_cummins #Quarkus compatibility libraries
242. @holly_cummins #Quarkus migration compatibility libraries
243. @holly_cummins #Quarkus migration compatibility libraries tooling
244. @holly_cummins #Quarkus migration compatibility libraries tooling ai skills
245. to the code! spring compatibility libraries
246. @holly_cummins #Quarkus
248. @holly_cummins #Quarkus “After a week of development with Quarkus, I was able to regain the same level of productivity as when I was developing with Spring Boot.” – Fawaz Paraïso, Decathlon
249. the double-win
251. co-benefits
252. co-benefits the double win
253. co-benefits the double win win-win
254. co-benefits the double win win-win twofer
255. co-benefits the double win win-win twofer überwinden
256. co-benefits the double win win-win twofer überwinden
258. cheaper at low load
259. cheaper at low load cheaper at high load
260. cheaper at low load cheaper at high load greener
261. cheaper at low load cheaper at high load greener more productive
262. cheaper at low load cheaper at high load greener more productive happier
263. @holly_cummins #Quarkus tl;dpa (too long didn’t pay attention) deployment density lower cloud bill frictionless development experience Medium Nano auto-provision services zero-con fi g live coding continuous testing developer UI greener happy, productive people
264. @holly_cummins #Quarkus stl;dpa (still too long didn’t pay attention) e ffi ciency quarkus can be packed ~2x more densely than spring boot quarkus can handle ~2x more tra ffi c on the same hardware developer experience quarkus creates joy quarkus boosts productivity by
265. @holly_cummins #Quarkus stl;dpa (still too long didn’t pay attention) e ffi ciency quarkus can be packed ~2x more densely than spring boot quarkus can handle ~2x more tra ffi c on the same hardware developer experience quarkus creates joy quarkus boosts productivity by 2x less infra
266. @holly_cummins #Quarkus stl;dpa (still too long didn’t pay attention) e ffi ciency quarkus can be packed ~2x more densely than spring boot quarkus can handle ~2x more tra ffi c on the same hardware developer experience quarkus creates joy quarkus boosts productivity by 40% more productive 2x less infra