Official account of Tencent Cloud Middleware. Focuses on microservices, messaging middleware and other cloud‑native technology trends, publishing product updates, case studies, and technical insights. Regularly hosts tech salons to share effective solutions.
This article introduces Apache Kafka’s KRaft (Kafka Raft) mode, explains its architectural differences from ZooKeeper‑based deployments, details essential configuration parameters, and provides a complete step‑by‑step procedure—including commands and utility tools—to set up and operate a KRaft cluster.
Tencent's Kona JDK 11 introduces a production‑ready ZGC implementation that reduces Java garbage‑collection stop‑the‑world pauses to under 10 ms, enabling ultra‑low‑latency online services across massive heaps while maintaining acceptable throughput, and the article details its design, tuning, and real‑world deployments.
The RoP (RocketMQ‑to‑Pulsar) plugin adds a pluggable protocol handler to Apache Pulsar, allowing RocketMQ clients to connect without code changes and leveraging Pulsar's features such as multi‑tenant storage, geo‑replication, and lightweight functions.
This article explains high availability fundamentals, defines availability, outlines design targets, presents common metrics such as MTBF, MTTR, MTTF, SA, RPO, RTO, discusses CAP theory, essential design elements, and answers practical Q&A on cost, architecture, fault tolerance, testing, and implementation guidance.
This article explains Apache Pulsar’s message storage architecture in BookKeeper, details the ledger and entry lifecycle, describes the multi‑layer caching read path, and outlines BookKeeper’s garbage‑collection process along with practical operational tips for avoiding disk‑heavy scenarios.
This article explains how TSF Mesh adapts Istio’s service‑mesh architecture to run both containerized and virtual‑machine workloads, detailing the modifications for sidecar injection, traffic hijacking, and service registration/discovery, and showing the underlying modules and code changes required.
Apache Pulsar’s built‑in Geo‑Replication lets multiple clusters across different regions synchronize data, offering both synchronous and asynchronous modes; this guide explains the three asynchronous patterns—full‑mesh, unidirectional, and failover—detailing required configurations, operational principles, and current limitations.
Facing challenges of distributed microservice architectures, Tencent’s Smart Retail team built a full‑link performance monitoring platform using Apache SkyWalking and the cloud‑native TSW service, detailing architecture, agent integration, deployment steps, and performance impact to guide similar observability implementations.
This article explains Apache Pulsar’s core architecture—including its message model, producer and consumer behavior, subscription types, storage hierarchy, acknowledgment mechanisms, cursor handling, backlog concepts, retention policies, and storage size calculations—helping readers understand why storage size can exceed backlog size.
This article explains how Apache Pulsar handles message retention, backlog quotas, and TTL policies, detailing the default behavior, configuration commands at the namespace level, practical examples, and troubleshooting tips for common production scenarios.
