Quarkus has its genesis in the JBoss community. JBoss has extensive experience of running applications on application servers (JBoss EAP, WildFly) and building reactive applications on the JVM (with Eclipse Vert.x for example). Due to its extension mechanism, Quarkus supports several Java frameworks (e.g. Hibernate, Camel, etc.) as well as specifications (e.g. a subset of Jakarta EE, or MicroProfile which is a set of specifications to develop microservices in Java). So, this fascicle is for the Java community as a whole and for those of you interested in microservice architectures.
The only requirements to follow and understand this fascicle are having a knowledge of Java and having some knowledge of relational databases and Docker. This fascicle concentrates on Quarkus 1.8.2.Final. Its structure will help you to discover this technology as well as helping you to further dive into it if you already have some experience of it.
As the number of services grows, the odds of any service failing also grows. If one of the involved services does not respond as expected, e.g. because of fragile network communication, we have to compensate for this exceptional situation. Eclipse MicroProfile Fault Tolerance allows us to build up our microservices architecture to be resilient and fault tolerant by design. This means we must not only be able to detect any issue but also to handle it automatically.