Book Image

Cloud-Native Development and Migration to Jakarta EE

By : Ron Veen, David Vlijmincx
Book Image

Cloud-Native Development and Migration to Jakarta EE

By: Ron Veen, David Vlijmincx

Overview of this book

Cloud-Native Development and Migration to Jakarta EE will help you unlock the secrets of Jakarta EE's evolution as you explore the migration and modernization of your applications. You’ll discover how to make your code compatible with the latest Jakarta EE version and how to leverage its modern features effectively. First, you’ll navigate the realm of cloud-native development as you demystify containers and get introduced to the Eclipse MicroProfile, a powerful tool in your toolkit. Next, you’ll take the bold step of transitioning your applications from local hardware to the limitless possibilities of the cloud. By following the author’s expert guidance to deploy your Jakarta EE applications on Microsoft Azure, you’ll gain hands-on experience in managing cloud resources. In the final leg of your journey, you’ll explore the world of serverless architecture. You’ll learn to design and run services that are truly serverless, harnessing the potential of the event-driven paradigm for scalability and cost-efficiency. By the end of this book, you’ll have mastered Jakarta EE and become a proficient cloud-native developer. Join us on this exciting journey of transformation and innovation as you pave the way for the future of Jakarta EE and cloud-native development.
Table of Contents (18 chapters)
1
Part 1: History of Java EE and Jakarta EE
4
Part 2: Modern Jakarta EE
8
Part 3: Embracing the Cloud
Appendix A: Java EE to Jakarta EE names
Appendix B: As a Service

MicroProfile Metrics

Our service has been configured, we can reason about its health, and we have resilience in place. The next thing we want to do is know how it performs. How many requests are handled, what is the longest execution time, and what is the average execution time? Questions like these can be asked, and answered, by MicroProfile Metrics.

Metrics is a vast area. In this section, we will only discuss the annotations that can be used. But know that you can define your own metrics programmatically.

Metrics offers a REST API that is, by specification, required to respond with metrics in Prometheus format. Optionally, implementations are allowed to respond in OpenMetrics format.

Metrics come in three scopes:

  • Base: Spec-described metrics that vendors may supply
  • Vendor: Vendor-specific metrics
  • Application: Application-specific metrics

The four metric annotations are as follows:

  • @Counted
  • @Gauge
  • @Metrics
  • @Timed

@Counted...