Sign In Start Free Trial

Book Overview & Buying
Table Of Contents
Feedback & Rating

Docker and Kubernetes for Java Developers

By : Jaroslaw Krochmalski, Krochmalski

3.5 (4)

Docker and Kubernetes for Java Developers

3.5 (4)

By: Jaroslaw Krochmalski, Krochmalski

Overview of this book

Imagine creating and testing Java EE applications on Apache Tomcat Server or Wildfly Application server in minutes along with deploying and managing Java applications swiftly. Sounds too good to be true? But you have a reason to cheer as such scenarios are only possible by leveraging Docker and Kubernetes. This book will start by introducing Docker and delve deep into its networking and persistent storage concepts. You will then proceed to learn how to refactor monolith application into separate services by building an application and then packaging it into Docker containers. Next, you will create an image containing Java Enterprise Application and later run it using Docker. Moving on, the book will focus on Kubernetes and its features and you will learn to deploy a Java application to Kubernetes using Maven and monitor a Java application in production. By the end of the book, you will get hands-on with some more advanced topics to further extend your knowledge about Docker and Kubernetes.

Preface

Preface

What this book covers

What you need for this book

Who this book is for

Conventions

Reader feedback

Customer support

Free Chapter

Introduction to Docker

Introduction to Docker

The idea behind Docker

Virtualization and containerization compared

Docker concepts - images and containers

Additional tools

Installing Docker

Summary

Networking and Persistent Storage

Networking and Persistent Storage

Networking

Networking commands

Creating and inspecting a network

Connecting a container to the network

Exposing ports and mapping ports

Persistent storage

Volume-related commands

Creating a volume

Removing a volume

Volume drivers

Summary

Working with Microservices

Working with Microservices

An introduction to microservices

Monolithic versus microservices

Maintaining data consistency

The Docker role

Kubernetes' role

When to use the microservice architecture

Summary

Creating Java Microservices

Creating Java Microservices

Introduction to REST

REST in Java

Coding the Spring Boot microservice

Running the application

Making calls

Spring Initializr

Summary

Creating Images with Java Applications

Creating Images with Java Applications

Dockerfile

Dockerfile instructions

Summary

Running Containers with Java Applications

Running Containers with Java Applications

Starting and stopping containers

Container running modes

Monitoring containers

Restart policies

Runtime constraints on resources

Running with Maven

Summary

Introduction to Kubernetes

Introduction to Kubernetes

Why do we need Kubernetes?

Basic Kubernetes concepts

Summary

Using Kubernetes with Java

Using Kubernetes with Java

Installing Minikube

Installing kubectl

Deploying on the Kubernetes cluster

Minikube addons

Cleaning up

Summary

Working with the Kubernetes API

Working with the Kubernetes API

API versioning

Authentication

Authorization

Admission control

Using the API

Swagger docs

Summary

Deploying Java on Kubernetes in the Cloud

Deploying Java on Kubernetes in the Cloud

Benefits of using the cloud, Docker, and Kubernetes

Installing the tools

Configuring Amazon AWS

Creating an administrative user

Creating the cluster

Summary

More Resources

More Resources

Docker

Kubernetes

Customer Reviews

3.5 (4)

5 star

25%

4 star

0

3 star

75%

2 star

0

1 star

0

Creating the cluster

We are going to create a simple cluster with one master node and two worker nodes. To do it using kops, we will need:

A user profile declared in ~/.aws/credentials (this is done automatically if you authenticate using aws configure).
An S3 bucket to store kops cluster state. In order to store the representation of our cluster and its state, we need to create a dedicated S3 bucket for kops to use. This bucket will become the source of truth for our cluster configuration.
DNS configured. This means we will need a Route 53 hosted zone in the same AWS account. Amazon Route 53 is a highly available and scalable cloud Domain Name System (DNS) web service. Kops will use it to create records needed by the cluster. If you are using newer kops (1.6.2 or later), then DNS configuration is optional. Instead, a gossip-based cluster can be easily created. For the purposes...

Search

Your notes and bookmarks