Enterprise Jakarta EE applications require extensive tooling during development - Maven for dependency management, full JDKs for compilation, and various build utilities. However, production environments need only the compiled application and runtime server like Payara Server or Payara Micro. Multi-stage Docker builds bridge this gap by separating build and runtime concerns, producing dramatically smaller and more secure container images for Payara deployments.

Almost any developer looking to leverage containers turns to Kubernetes (K8s) for orchestration. However, with its complexity comes security risks, particularly misconfigurations, which remain one of the most critical attack vectors in cloud-native environments. In effect, K8s misconfigurations can lead to data breaches, privilege escalations and service disruptions. 

This blog examines key technical security challenges associated with K8s and demonstrates how to mitigate these risks through platform engineering. 

One major issue when developing modern enterprise applications is the "works on my machine" problem: when an application works well on your machine but is not functional in production or even on a colleague's machine. An even more prevalent problem is to maintain the quality of ever-changing applications during development and maintenance. 

This is especially prevalent when Jakarta EE applications are developed and not properly tested in an isolated and cohesive manner. Proper integration testing helps to avoid both the "works on my machine" problem, and ensures developers can change the application effectively without breaking it. However often teams struggle with it, due to a lack of standardized testing solutions and the unpredictability of real-world conditions. 

Here, I present an effective method for Jakarta EE integration testing, using Payara Platform and Testcontainers in my example.

Payara Microでは、Webアプリケーションを自己完結型で簡単に実行することができます。2016年5月のPayara Serverリリースからは、WARファイルの内容とPayara Microを構成するクラスやリソースを束ねる “Uber JAR” を作成する簡単な方法があります。

この “Uber” Jarは、Dockerコンテナ内でアプリケーションを実行するための最良の方法ではないことに注意してください。アプリケーションに小さなコード変更を加えるたびに、バイナリ全体のアップデートが必要になるためです。より良い方法は、Payara Microインスタンスを起動して、インストールが必要なアプリケーションを指定することです。詳細については Payara Micro Docker Image documentation をご覧ください。

(最終更新日 2021/04/06)

Creating a Docker image is not that difficult. The Dockerfile script contains a few commands that define and prepare your image that will be run by the engine as a container.

Docker is a platform which makes it easier to create, deploy and run your applications using containers. A container bundles all the software needed to run it. By packaging the required dependencies, it makes it easy to run it on any machine, regardless of small configuration differences. This article will explain more about introducing Docker. 

Dockerとは? DockerとPayara Server/Payara Microを一緒に使うには?

Introduction

With Container orchestration tools like Kubernetes and Docker Swarm, you can add instances quite easily. Depending on the type of clustering you need or use for your application, some scenarios are easier to implement than others.

Several Cloud Providers have the possibility to run your Payara Platform Docker Images on their infrastructure. In this blog, I will describe to you how you can run your application on Microsoft Azure using a Docker Container. All the steps required to perform this are described using the Azure Portal (web-based application) and the Azure Command line.

Kubernetes is most commonly used with Docker managed containers, although it doesn't strictly depend on it. Kubernetes defines a Container Runtime Interface (CRI) that container platforms must implement in order to be compatible. These implementations are colloquially known as "shims". This makes Kubernetes platform agnostic so that instead of Docker you're free to use other platforms with corresponding shims, such as CRI-O or KataContainers.