Quarkus vs. Spring Boot

The idea behind Quarkus is to have small containers that can be launched in just a few seconds. This allows for rapid scaling up and down, adapting resource usage to demand by automatically adding or removing containers, which makes costs especially effective in a pay-per-use cloud environment. If we take a medium-sized implementation built with Spring Boot, we would need to segment the application into several sub-projects to achieve the desired effect. Even for a new implementation, the question is: what advantages would Quarkus bring? In the case of one or more significant modules that need to scale quickly, the benefits are measurable. However, for an implementation with predictable usage and stable traffic volumes, there is no advantage to being faster.

Springboot mutlipart upload

The upload works very well for many use cases but I want to handle the upload with an AJAX client. As soon as the upload exceeds the limits the embedded servlet container fires an unhandled exception and the Javascript client doesn't receive any suitable answer from the server.

Webfonts mime types with Springboot

Springboot (1.2.5) per default doesn't have mime mapping for WEB fonts (glyphicons).