Kubernetes Native Microservices with Quarkus and MicroProfile
Manning Early Access Program
Kubernetes Native Microservices: With Quarkus and MicroProfile provides an essential understanding of what it takes to develop cloud-native applications using modern tools such as microservices that utilize and integrate with Kubernetes features naturally and efficiently. The result is a productive developer experience that is consistent with the expectations of Kubernetes platform administrators.
Entire books are available on Quarkus, Microservices, MicroProfile, Spring, and Kubernetes. However, they tend to focus on each specific topic.
Kubernetes Native Microservices: With Quarkus and MicroProfile will show you how to combine these technologies into an effective and integrated development and deployment stack.
By reading these early release chapters, you will:
- Understand what microservices are and how they have evolved over the last decade as a popular enterprise software architecture.
- Dive into the history and overview of MicroProfile and its growth into a significant collection of microservices-related specifications and introduce Quarkus as a Java runtime that supports these technologies.
- Get an introduction to core Kubernetes concepts and why they make Kubernetes an ideal microservices deployment platform.
- Learn how to unite Java, MicroProfile, Quarkus, and Kubernetes to build fast, efficient applications.
- Get step-by-step instructions on how to make code changes in Quarkus Live Coding.
- Learn how to develop Java microservices with Quarkus and Microprofile that target Kubernetes as a deployment environment.
In short, you will learn what you need to build and deploy Kubernetes native microservices in a productive fashion.
Full book will be available for download in Fall, 2021.
There are multiple facets to testing creation. In addition to verifying creation of the new account, the test needs to ensure that the list of all accounts includes the new account. When including tests for mutating the state within a service, it becomes necessary to order the execution sequence of tests.
Why is it necessary to order the test execution? When there is a test to create, delete, or update the state within a service, it will impact any tests that read the state. For instance, in the above test to retrieve all accounts, Listing 2.14, the expectation is it returns three accounts. However, when the test method execution order is non-deterministic, i.e. not in a defined order, it's possible for the test creating an account to execute before Listing 2.14, causing it to fail by finding four accounts.