book

Kubernetes Native Microservices with Quarkus and MicroProfile

by Kenneth Finnigan, John Clingan

January 2022

Intermediate to advanced

328 pages

9h 8m

English

Manning Publications

Read now

Unlock full access

prefaceacknowledgmentsabout this bookWho should read this book?How this book is organized: A road mapAbout the codeliveBook discussion forumabout the authorsabout the cover illustration
1.1 What is a microservice?1.1.1 The rise of microservices1.1.2 Microservices architecture1.1.3 The need for microservices specifications1.2 MicroProfile1.2.1 History of MicroProfile1.2.2 MicroProfile community core principles1.3 Quarkus1.3.1 Developer joy1.3.2 MicroProfile support1.3.3 Runtime efficiency1.4 Kubernetes1.4.1 Introduction to Kubernetes1.5 Kubernetes-native microservicesSummary
2.1 Creating a project2.2 Developing with live coding2.3 Writing a test2.4 Creating a native executable2.5 Running in Kubernetes2.5.1 Generating Kubernetes YAML2.5.2 Packaging an application2.5.3 Deploying and running an applicationSummary
3.1 MicroProfile Config architecture overview3.2 Accessing a configuration3.3 The Bank service3.3.1 Creating the Bank service3.3.2 Configuring the Bank service name field3.4 Configuration sources3.5 Configuring the mobileBanking field3.6 Grouping properties with @ConfigProperties3.7 Quarkus-specific configuration features3.7.1 Quarkus configuration profiles3.7.2 Property expressions3.7.3 Quarkus ConfigMapping3.7.4 Run-time vs. build-time properties3.8 Configuration on Kubernetes3.8.1 Common Kubernetes configuration sources3.8.2 Using a ConfigMap for Quarkus applications3.8.3 Editing a ConfigMap3.8.4 Kubernetes SecretsSummary

4.1 Data sources4.2 JPA4.3 Simplifying database development4.3.1 Active record approach4.3.2 Data repository approach4.3.3 Which approach to use?4.4 Deployment to Kubernetes4.4.1 Deploying PostgreSQL4.4.2 Package and deploySummary
5.1 What is MicroProfile REST Client?5.2 Service interface definition5.2.1 CDI REST client5.2.2 Programmatic REST client5.2.3 Choosing between CDI and a programmatic API5.2.4 Asynchronous response types5.3 Customizing REST clients5.3.1 Client request headers5.3.2 Declaring providersSummary
6.1 The growing role of developers in application health6.2 MicroProfile Health6.2.1 Liveness vs. readiness6.2.2 Determining liveness and readiness status6.3 Getting started with MicroProfile Health6.3.1 Account service MicroProfile Health liveness6.3.2 Creating an Account service liveness health check6.3.3 Account service MicroProfile Health readiness6.3.4 Disabling vendor readiness health checks6.3.5 Creating a readiness health check6.3.6 Quarkus health groups6.3.7 Displaying the Quarkus Health UI6.4 Kubernetes liveness and readiness probes6.4.1 Customizing health check properties6.4.2 Deploying to Kubernetes6.4.3 Testing the readiness health check in KubernetesSummary
7.1 Resilience strategies overview7.2 Executing a method under a separate thread with @Asynchronous7.3 Constraining concurrency with bulkheads7.4 Updating a TransactionService with a bulkhead7.5 Exception handling with fallbacks7.6 Defining execution timeouts7.7 Recovering from temporary failure with @Retry7.8 Avoiding repeated failure with circuit breakers7.8.1 MicroProfile Fault Tolerance: @CircuitBreaker7.8.2 How a circuit breaker works7.8.3 Updating the TransactionService to use @CircuitBreaker7.8.4 Testing the circuit breaker7.9 Overriding annotation parameter values using properties7.10 Deploying to KubernetesSummary
8.1 Reactive example8.2 What is Reactive Streams?8.2.1 Publisher, Subscriber, and Processor8.2.2 The importance of back pressure8.3 Reactive Messaging in Quarkus8.3.1 Bridging from imperative to reactive with emitters8.3.2 What about blocking?8.3.3 Testing “in memory”8.4 How does it work?8.4.1 MicroProfile Reactive Messaging specification8.4.2 Message content and metadata8.4.3 Messages in the stream8.5 Deploying to Kubernetes8.5.1 Apache Kafka in Minikube8.5.2 Putting it all togetherSummary
9.1 Quarkus/Spring API compatibility overview9.2 Spring dependency injection and configuration compatibility9.2.1 Setting up the Spring Cloud Config Server9.2.2 Using the Spring Config Server as a configuration source9.2.3 Converting the Bank service to use Spring Configuration APIs9.3 Quarkus/Spring Web API compatibility9.4 Quarkus/Spring Data JPA compatibility9.5 Deploying to Kubernetes9.6 How Quarkus implements Spring API compatibility9.7 Common Quarkus/Spring compatibility questions9.8 Comparing the Spring Boot and Quarkus startup processesSummary
10.1 The role of metrics in a microservices architecture10.2 Getting started with MicroProfile Metrics10.2.1 Graphing metrics with Prometheus and Grafana10.2.2 MicroProfile Metrics10.2.3 Instrumenting the Account service10.2.4 Instrumenting the TransactionService10.2.5 Creating business metrics10.2.6 MicroProfile Fault Tolerance and JAX-RS integration with MicroProfile Metrics10.2.7 Micrometer metrics10.2.8 Simulating a busy production systemSummary
11.1 How does tracing work?11.2 Jaeger11.2.1 Trace sampling11.2.2 Setting up the Minikube environment11.2.3 Installing Jaeger11.2.4 Microservice tracing with Jaeger11.3 Tracing specifications11.3.1 OpenTracing11.3.2 What is MicroProfile OpenTracing?11.3.3 OpenTelemetry11.4 Customizing application tracing11.4.1 Using @Traced11.4.2 Injecting a tracer11.4.3 Tracing database calls11.4.4 Tracing Kafka messagesSummary
12.1 Viewing OpenAPI documents with Swagger UI12.1.1 Enabling OpenAPI12.1.2 Swagger UI12.2 MicroProfile OpenAPI12.2.1 Application information12.2.2 Customizing the schema output12.2.3 Defining operations12.2.4 Operation responses12.2.5 Tagging operations12.2.6 Filtering OpenAPI content12.3 Design-first development12.3.1 OpenAPI file base12.3.2 Mixing the file and annotations12.4 Code first or OpenAPI first?Summary
13.1 Authorization and authentication overview13.2 Using file-based authentication and authorization13.3 Authentication and authorization with OpenID Connect13.3.1 Introduction to OpenID Connect (OIDC)13.3.2 OIDC and Keycloak13.3.3 Accessing a protected resource with OpenID Connect13.3.4 Testing the Code Authorization Flow13.4 Json Web Tokens (JWT) and MicroProfile JWT13.4.1 JWT header13.4.2 JWT payload13.4.3 JWT signature13.5 Securing the Transaction service using MicroProfile JWT13.6 Propagating the JWT13.6.1 Secure an Account service endpoint13.6.2 Propagating JWT from the Transaction service to the Account service13.7 Running the services in KubernetesSummary

Content preview from Kubernetes Native Microservices with Quarkus and MicroProfile

12 API visualization

This chapter covers

Generating OpenAPI (previously known as Swagger UI) specifications for a project
Accessing OpenAPI project specifications
Visually inspecting project endpoints with the Swagger UI
Utilizing the design-first approach to developing APIs—the process of creating an API design before implementing it with code

Originally developed in 2010 as a way for defining machine-readable interfaces to describe RESTful services, in 2016, the Swagger specification was rebranded as the OpenAPI specification under a new OpenAPI initiative sponsored by the Linux Foundation. Other benefits to an OpenAPI specification of a service follow: