JavaScript singe-page application can mimic sub pages via an internal routing mechanism. For this feature to still work on a page reload, a filter must be implemeneted in a Quarkus backend which redirects certain 404 errors to the index page.

The best way to become familiar with Quarkus as a Spring developer is to look at what is required to migrate a Spring application to a Quarkus application. This way, we can build a deep understanding of the concepts and components of Quarkus.

We are looking at a project architecture that combines the maven and npm toolchains to bundle a web framework frontend and a Quarkus backend into one distributable JAR.

This article presents an implementation strategy to create a custom JSON, HTML, or text error page, via a centralized error response handling in an exception mapper or a response filter.

Implementation strategies for the "synchronizer token", "cookie-to-header token" and "double submit cookie" pattern to prevent CSRF attacks in Quarkus.

In this article we will look at the mechanisms provided by the MicroProfile Config API to define custom configurations source in Quarkus.

An in-depth description of all built-in bean scopes provided by Quarkus, the creation of custom scopes, and how to force the initialization of a bean.