Monitoring across frameworks

• launcher

  1 41 5.3 Java

  Launcher - MicroProfile implementation (by fujitsu)

  

Interestingly enough, I found at least two Microprofile implementations in the form of libraries - as opposed to a full-fledged application server: SmallRye and Launcher by Fujitsu. Providers of application servers, and developers, can use those dependencies instead of re-implementing the specification themselves. That's the approach that Quarkus follows.

• Spring Boot

  166 72,782 10.0 Java

  Spring Boot

  

Spring Boot is the framework that started the trend regarding providing monitoring capabilities. To enable them is only a matter of adding a single dependency known as the Actuator:

• WorkOS

  workos.com sponsored

  The modern identity platform for B2B SaaS. The APIs are flexible and easy-to-use, supporting authentication, user identity, and complex enterprise features like SSO and SCIM provisioning.

  

• Quarkus

  127 13,072 10.0 Java

  Quarkus: Supersonic Subatomic Java.

  

Last but not least comes Quarkus. Quarkus' approach differs from Spring Boot's and Micronaut's: it's doesn't implement endpoints itself but relies on a third-party dependency. Before getting to the core, let me digress a bit.

• Micronaut

  50 5,950 9.9 Java

  Micronaut Application Framework

  

Micronaut also offers monitoring endpoints. Those endpoints mostly map to those provided by Spring Boot with a few exceptions.

Suggest a related project