Introduction to gRPC
gRPC is an inter-process communication technology that allows you to connect, invoke, operate, and debug distributed applications as easily as making a local function call.
gRPC is an inter-process communication technology that allows you to connect, invoke, operate, and debug distributed applications as easily as making a local function call.
There is an old Java project. After I upgrade the version of JDK from 8 to 21 in IntelliJ IDEA, and run the main() method in IntelliJ IDEA, an error occurs.
In this post, I will cover common uses of Kubernetes.
In the previous post Introduction to Kubernetes, I have introduced Kubernetes common concepts. In this post, I will cover how to get started with Kubernetes. It includes the following content: how to set up your Kubernetes cluster and how to run your first application on Kubernetes.
Kubernetes (K8s) is an open-source container orchestration platform originally developed by Google and now maintained by the Cloud Native Computing Foundation (CNCF).
It automates the deployment, scaling, and management of containerized applications. Instead of running containers manually, Kubernetes provides a framework to run them reliably and at scale across clusters of machines.
In this post, I will introduce the common concepts of Kubernetes.
After creating a Java project, you usually need to do some initialization work. In this article, I will cover common initialization tasks for Java projects.
GraalVM Native Image is a tool that takes your Java (or other JVM-based) application and compiles it ahead of time (AOT) into a standalone, platform-specific executable.
JLink is a tool included with the JDK (Java Development Kit) starting from Java 9 that lets you create a custom, minimal Java runtime containing only the modules your application actually needs.
Instead of using the full 200+ MB JDK/JRE, you can use JLink to generate a slim, app-specific JRE image.
In this post, I will introduce the Fully Dockerized Gradle Workflow.
Containers share the host kernel, which means that the code that’s running inside the container must be compatible with the host’s architecture. This is why you can’t run a linux/amd64 container on an arm64 host (without using emulation), or a Windows container on a Linux host.