Book Image

Hands-On Enterprise Java Microservices with Eclipse MicroProfile

By : Cesar Saavedra, Heiko W. Rupp, Jeff Mesnil, Pavol Loffay, Antoine Sabot-Durand, Scott Stark
Book Image

Hands-On Enterprise Java Microservices with Eclipse MicroProfile

By: Cesar Saavedra, Heiko W. Rupp, Jeff Mesnil, Pavol Loffay, Antoine Sabot-Durand, Scott Stark

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.
Table of Contents (18 chapters)
Free Chapter
1
Section 1: MicroProfile in the Digital Economy
4
Section 2: MicroProfile's Current Capabilities
9
Section 3: MicroProfile Implementations and Roadmap
11
Section 4: A Working MicroProfile Example
13
Section 5: A Peek into the Future

Chapter 6

  1. No: by default, any REST endpoint will have OpenAPI generated for it even if none of the MP OpenAPI annotations are used.
  2. 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.
  3. 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.
  4. 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.
  5. 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.
  6. One way is to register a ClientHeadersFactory implementation. Another is to list the headers in the org.eclipse.microprofile.rest.client.propagateHeaders...