Why Floci is built in Java (and why that's the right call in 2026)
Floci is built in Java due to specific constraints that prioritize performance and efficiency. The advancements in Java from version 8 to 25, including features like virtual threads and compact object headers, make it suitable for Floci's requirements. Additionally, the use of Quarkus and GraalVM allows for a significantly smaller and faster application without the overhead of a traditional JVM.
- ▪Floci requires a 24ms cold start and small memory usage, which influenced the choice of Java as the programming language.
- ▪Java has evolved significantly, introducing features that enhance concurrency and reduce boilerplate code, making it more modern and efficient.
- ▪The combination of Quarkus and GraalVM enables Floci to run as a native binary, resulting in faster startup times and reduced memory footprint compared to traditional JVM applications.
Opening excerpt (first ~120 words) tap to expand
try { if(localStorage) { let currentUser = localStorage.getItem('current_user'); if (currentUser) { currentUser = JSON.parse(currentUser); if (currentUser.id === 805260) { document.getElementById('article-show-container').classList.add('current-user-is-article-author'); } } } } catch (e) { console.error(e); } Hector Ventura Posted on May 16 • Originally published at dev.to Why Floci is built in Java (and why that's the right call in 2026) #aws #java #quarkus #opensource I get this question every week: "Why did you build Floci in Java? Why not Go, Rust, or Python like LocalStack?" It's a fair question. And the short answer is: the constraints picked the language, not the other way around.
…
Excerpt limited to ~120 words for fair-use compliance. The full article is at DEV.to (Top).
Discussion
0 commentsMore from DEV.to (Top)
