Follow me! Discussing software architecture and development, AIGC and AI Agents... Sometimes sharing insights on IT professionals' life experiences.
This guide outlines practical Redis best‑practice rules covering key naming conventions, data‑size limits, expiration strategies, script and transaction usage, client connection handling, and security measures to help you build fast, stable, and secure production systems.
This article explains the fundamentals of Java threads and thread pools, details the configurable parameters of ThreadPoolExecutor, highlights the pitfalls of the Executors factory methods, and provides concrete recommendations and code examples for safely tuning thread pools across different workload types.
This article explains Redis's atomic counter commands (INCR, INCRBY, DECR, DECRBY), highlights their pitfalls such as missing TTL and concurrency issues, and presents practical design solutions—including SET NX+EX initialization, double‑TTL compensation, retry queues, fallback strategies, and performance optimizations like Lua scripting and pipelining.)
Google’s open‑source A2A (Agent‑to‑Agent) protocol, unveiled at Google Cloud Next 2025, defines a standardized, secure, Web‑based framework that lets heterogeneous AI agents discover each other, negotiate interactions, and manage cross‑agent tasks, supporting multimodal communication, long‑running jobs, and push notifications.
Understanding high‑availability architectures involves mastering replication and fail‑over, balancing RTO and RPO, and choosing among four patterns—Active‑Standby, Active‑Active, Cold Standby, and Hot Standby—each with distinct synchronization, load‑balancing, and cost considerations for reliable system design.
This article explains why simple GET‑modify‑SET inventory updates cause overselling in flash‑sale spikes and presents several Redis‑based solutions—including Lua scripts, WATCH‑based optimistic locks, distributed SETNX locks, and asynchronous queue processing—detailing their implementation, advantages, and trade‑offs.
Kafka 4.0 introduces KRaft, a ZooKeeper‑free metadata layer built on the Raft consensus algorithm, detailing role transitions, leader election, log replication, controller and broker responsibilities, and fault‑tolerance mechanisms, enabling a more scalable and self‑managed architecture for large‑scale distributed streaming.
This article compares Kafka, RocketMQ, and RabbitMQ, detailing their architectures, performance characteristics, strengths, and ideal use‑cases to help engineers select the most suitable message‑queue solution for high‑throughput, fault‑tolerant, and real‑time processing scenarios.
Apache Kafka 4.0 eliminates Zookeeper with the KRaft consensus protocol, upgrades Java requirements to 17, introduces a next‑generation consumer rebalance protocol, adds Share Group queue semantics, and bundles numerous performance, security, and API improvements for modern streaming workloads.
Explore the BGE (BAAI General Embedding) family—including v1, v1.5, M3, Multilingual Gemma2, and EN‑ICL—detailing their multilingual capabilities, model variants, token limits, optimal use cases, and step‑by‑step installation and Python usage instructions with code examples for embedding generation and similarity scoring.
