Hands-On Enterprise Java Microservices with Eclipse MicroProfile

By : Saavedra, Heiko W. Rupp , Mesnil, Loffay, Sabot-Durand, Stark

5 (1)

Buy this Book

Hands-On Enterprise Java Microservices with Eclipse MicroProfile

5 (1)

By: Saavedra, Heiko W. Rupp , Mesnil, Loffay, Sabot-Durand, Stark

Buy this Book

Overview of this book

Eclipse MicroProfile has gained momentum in the industry as a multi-vendor, interoperable, community-driven specification. It is a major disruptor that allows organizations with large investments in enterprise Java to move to microservices without spending a lot on retraining their workforce. This book is based on MicroProfile 2.2, however, it will guide you in running your applications in MicroProfile 3.0. You'll start by understanding why microservices are important in the digital economy and how MicroProfile addresses the need for enterprise Java microservices. You'll learn about the subprojects that make up a MicroProfile, its value proposition to organizations and developers, and its processes and governance. As you advance, the book takes you through the capabilities and code examples of MicroProfile’s subprojects - Config, Fault Tolerance, Health Check, JWT Propagation, Metrics, and OpenTracing. Finally, you’ll be guided in developing a conference application using Eclipse MicroProfile, and explore possible scenarios of what’s next in MicroProfile with Jakarta EE. By the end of this book, you'll have gained a clear understanding of Eclipse MicroProfile and its role in enterprise Java microservices.

Preface

Who this book is for

What this book covers

To get the most out of this book

Get in touch

Free Chapter

Section 1: MicroProfile in the Digital Economy

Introduction to Eclipse MicroProfile

Enterprise Java microservices

Forces that fuel the digital economy

Introducing Eclipse MicroProfile

MicroProfile value proposition

Summary

Questions

Governance and Contributions

Current Eclipse MicroProfile governance

MicroProfile Starter

Summary

Questions

Section 2: MicroProfile's Current Capabilities

MicroProfile Config and Fault Tolerance

Understanding Eclipse MicroProfile Config

Understanding Eclipse MicroProfile Fault Tolerance

Summary

Questions

Further reading

MicroProfile Health Check and JWT Propagation

Technical requirements

Understanding health checks and how MicroProfile handles them

Using JSON Web Token Propagation in MicroProfile

Summary

Questions

MicroProfile Metrics and OpenTracing

MicroProfile Metrics

MicroProfile OpenTracing

Summary

Questions

MicroProfile OpenAPI and Type-Safe REST Client

Introduction to MicroProfile OpenAPI and its capabilities

Introduction to the MicroProfile REST Client and its capabilities

Summary

Questions

Section 3: MicroProfile Implementations and Roadmap

MicroProfile Implementations, Quarkus, and Interoperability via the Conference Application

Current MicroProfile implementations

Quarkus

MicroProfile interoperability – the conference application

Summary

Questions

Section 4: A Working MicroProfile Example

A Working Eclipse MicroProfile Code Sample

Technical requirements

Sample architecture of a multiservice MicroProfile application

Summary

Questions

Chapter 6

No: by default, any REST endpoint will have OpenAPI generated for it even if none of the MP OpenAPI annotations are used.
Yes: you can choose to use as many or as few of the MP OpenAPI annotations as you wish, to represent the REST endpoints in your microservice.
The notion is that you predefine the expected contracts of your endpoints and encapsulate these in OpenAPI documents that can be bundled with your microservice.
No: you just need to know what the formats of the request and response are, and then you can create your own type-safe interface.
By using the .../mp-rest/url MP Config setting, where ... is either the interface name of the type-safe interface or the configKey passed to the RegisterRestClient annotation.
One way is to register a ClientHeadersFactory implementation. Another is to list the headers in the org.eclipse.microprofile.rest.client.propagateHeaders...