1 views collected around this technical thread.
This article explains Docker’s fundamental technologies—how Linux namespaces provide process, network, and filesystem isolation while cgroups enforce resource limits such as CPU, memory, I/O, and process counts—offering a concise guide for building secure, efficient containerized applications.
This article provides a comprehensive guide to Docker, covering its core concepts, installation steps for CentOS, macOS, and Windows, essential Docker commands, detailed Dockerfile instructions, and an introduction to Docker Compose with practical examples.
The article explains how the vivo Internet Big Data team containerized offline Spark jobs and deployed them with the Spark Operator on a mixed online‑offline Kubernetes cluster, using elastic scheduling and resource‑over‑subscription to boost CPU utilization by 30‑40% and handle over 100,000 daily tasks.
The article examines why deploying MySQL in Docker containers can lead to data‑security, performance, state‑management and resource‑isolation problems, outlines mitigation strategies, discusses scenarios where containerization is feasible, and concludes with a call for community discussion while also featuring promotional material for AI‑related services.
This guide explains how to locally deploy the DeepSeek large‑language model using Ollama on Windows, macOS, and Linux, configure model storage and CORS, build personal and enterprise RAG knowledge bases with AnythingLLM and Open WebUI, and integrate the model into a Spring AI application via Docker and Docker‑Compose.
The article compares cloud‑native and traditional architectures, explaining how microservices, containers, and DevOps enable greater flexibility, scalability, resource efficiency, fault tolerance, and faster market response, while outlining migration best practices for enterprises transitioning to the cloud.
Xiaohongshu’s cloud‑native team transformed its over‑90% containerized services by introducing resource‑pooled mixed deployment, fine‑grained unified scheduling, and an elastic container pool with global HPA and cluster autoscaling—driving 35% of resources to mixed use, tens of millions of daily core‑hours, and roughly 30% cost savings while preparing for hybrid‑cloud expansion and FinOps.
This article explains Docker fundamentals, outlines why containers are popular, and walks through a practical example of reducing a React app's Docker image size from 1.16 GB to 22 MB using a lightweight Alpine base, multi‑stage builds, and an Nginx final stage.
The article outlines several reasons why running MySQL in Docker containers is problematic—data security, performance bottlenecks, statefulness, and resource isolation—while also promoting a ChatGPT community and related services.
This article explains the fundamentals of containerization by reviewing virtualization concepts, detailing Docker's architecture and Dockerfile syntax, and then introduces Kubernetes' control‑plane and node components, providing step‑by‑step examples for deploying a simple Nginx service and a Java web application on a K8s cluster, both manually and with automation tools.
The article details the background, architectural analysis, multi‑tenant redesign, engine selection enhancements, compatibility adaptations, stability fixes, containerized deployment, performance optimizations, and measurable business outcomes of the Intelligent Acceleration Engine upgrade using Apache Kyuubi and StarRocks within the 58 big data platform.
By switching to a lightweight Alpine base, employing multi‑stage builds to separate compilation from runtime, and finally serving the React app with an Nginx Alpine image, Docker images can be reduced from over a gigabyte to roughly twenty‑two megabytes, enabling efficient, minimal‑footprint container deployment.
This tutorial demonstrates how to reduce Docker image size for a ReactJS project by switching to Alpine‑based Node images, applying multi‑stage builds, and finally serving the static build with Nginx, shrinking the image from over 1.4 GB to just 22 MB while preserving functionality.
The article examines why deploying MySQL in Docker containers can be problematic, highlighting data‑security risks, performance bottlenecks, state‑management challenges, and limited resource isolation, while also noting specific scenarios where containerizing MySQL might still be viable.
This article lists ten frequent Docker anti‑patterns—such as using large base images, running as root, and neglecting health checks—and provides practical solutions to improve container efficiency, security, and scalability.
This article explains why using Docker to host MySQL is generally discouraged, highlighting challenges in database scaling due to container‑exclusive storage, difficulties sharing data files, and memory contention among containers, while also outlining possible synchronization solutions and scenarios where containerized MySQL may still be viable.
This guide explains Dockerfile fundamentals, key instructions, and best‑practice techniques—such as using minimal base images, reducing layers, leveraging multi‑stage builds, and securing secrets—to help you create smaller, faster, and more secure container images.
The article examines why applications experience slower performance after being containerized on Kubernetes, presenting benchmark comparisons, analyzing increased soft‑interrupt overhead due to the Calico ipip overlay, and proposing network optimizations such as ipvlan modes and Cilium to restore efficiency.
This article introduces ten indispensable tools for operations engineers, detailing each tool's functionality, ideal use cases, key advantages, and real‑world examples, plus code snippets and visual illustrations to help you choose the right solution for automation, monitoring, configuration, and container management.
This article compares a cloud‑provider’s closed‑source Batch compute service with the open‑source, serverless Argo Workflows platform, demonstrating how each can orchestrate multi‑stage containerized data‑processing pipelines, detailing configuration, job definitions, dependency handling, and operational trade‑offs.