This tutorial walks through adding Spring Cloud Gateway as a single entry point for client calls to multiple microservices, covering why a gateway is needed, project structure, dependency and configuration setup, global logging and authentication filters, startup verification, and common pitfalls with solutions.
The article explains how the longstanding web architecture that separates stateful databases from stateless compute is being challenged by large language models and AI agents, which introduce long‑running, stateful, bidirectional workflows, exposing the need for new routing primitives such as persistent pub/sub channels rather than traditional HTTP‑load‑balancer setups.
This article shows how to replace verbose WebClient/Nacos calls with declarative OpenFeign in a Spring Cloud microservice setup, reducing code by about 80%, improving readability, adding automatic load balancing, retries, logging, and circuit‑breaker support, and provides step‑by‑step configuration, code examples, and common pitfalls.
Facing hour‑level demands for new educational tools, Yuanfudao created the internal Rush platform that lets any employee describe a need in natural language and instantly receive a full‑stack application, thanks to Volcano Supabase’s AI‑native BaaS, dramatically cutting development time, cost, and operational complexity.
After finishing the Spring Boot source‑code series, the author launches a refreshed Spring Cloud microservices tutorial built on Spring Boot 3.x, Jakarta EE, GraalVM native images, full production‑grade demos, Kubernetes deployment, observability and performance testing, outlining a 12‑episode roadmap.
Nacos 3.2 expands beyond a micro‑service registry to become a unified AI asset governance platform, introducing AI Registry, MCP Registry, a three‑layer Skill security sandbox, Copilot assistance, and A2A protocol integration for seamless enterprise AI adoption.
This guide walks through the challenges of turning a locally built prototype into a globally accessible site and shows how TRAE AI IDE combined with IGA Pages enables one‑click, serverless deployment, GitHub integration, edge functions, custom domains, and sustainable CI/CD workflows for developers and product teams.
This guide walks operators through a systematic, step‑by‑step process for diagnosing Docker container startup failures, covering status checks, log inspection, detailed use of docker inspect, and categorized troubleshooting of image, configuration, resource, permission, network, and volume issues with concrete commands and examples.
The article dissects OpenAI's engineering approach to delivering low‑latency voice AI at scale, explaining why WebRTC was chosen, how a Relay + Transceiver split solves Kubernetes integration challenges, the use of ICE ufrag for deterministic routing, and how global relay and implementation choices reduce perceived latency.
The article explains why the Kubernetes Dashboard has been deprecated due to security and multi‑cluster limitations, and introduces Headlamp as the officially endorsed, lightweight web UI that offers multi‑cluster management, strict RBAC enforcement, and extensible plugins, with simple installation steps.
This article walks Kubernetes operators through a systematic investigation of NotReady node symptoms, explaining the kubelet status mechanism, detailing each diagnostic step—from verifying node conditions with kubectl to checking kubelet, container runtime, resources, network, and certificates—and providing concrete remediation and preventive measures.
The article explains how GooseFS integrates with the Lance vector format to overcome the IO bottlenecks of object storage, detailing native acceleration mechanisms such as namespace catalog services, event‑driven warm caching, automatic compaction, native transactions, and page‑level caching that together deliver up to three‑fold performance gains for AI workloads.
This article walks through a practical implementation of gray (canary) release in a Spring Cloud ecosystem using Nacos for service discovery, Spring Cloud Gateway for routing, Ribbon (or Spring Cloud LoadBalancer) for load balancing, and custom interceptors to control traffic based on request metadata.
This article reviews the entire Spring Cloud microservices series, presents a full technology stack diagram, outlines production‑grade best practices for service decomposition, configuration, remote calls, rate limiting, databases, logging and monitoring, lists common pitfalls, offers performance‑tuning tips, discusses the pros and cons of microservices, and points to future directions such as service mesh, serverless and cloud‑native adoption.
This article explains why traditional deployment is problematic, then walks through building Docker images, composing services with Docker‑Compose, deploying to a Kubernetes cluster, setting up CI/CD pipelines, and addressing common pitfalls such as slow starts and service discovery failures.
This article provides a systematic, layer‑by‑layer troubleshooting guide for Kubernetes service connectivity problems, covering pod health, service and endpoint configuration, kube‑proxy rules, CNI plugins, Ingress controllers, DNS resolution, and NetworkPolicy, with concrete commands, examples, and preventive scripts.
RocketMQ 5.0 replaces the monolithic Broker with a stateless Proxy layer that decouples compute from storage, solves scalability, multi‑protocol and cloud‑native adaptation challenges, and is demonstrated through detailed architecture comparisons, Java code samples, and two real‑world IoT and finance case studies showing significant performance and cost benefits.
Tank OS, an open‑source project by Red Hat chief engineer Sally O'Malley, combines Fedora and OpenClaw into a bootable, root‑less container image, offering consistent, secure, and scalable management of enterprise AI agents through bootc technology.
A two‑day investigation of intermittent packet loss in a hybrid‑cloud Kubernetes environment revealed that an oversized VXLAN MTU caused fragmentation, prompting a step‑by‑step analysis of MTU fundamentals, diagnostic commands, Cilium configuration changes, and best‑practice recommendations for cloud‑native networks.
The article explains that running production Kubernetes clusters without regular backup and recovery plans exposes businesses to severe risks such as cluster failures, data loss, and prolonged downtime, and it details practical etcd physical and Velero logical backup strategies to mitigate these threats.
