This article examines why many game companies avoid microservice architectures, highlighting the real‑time latency, stateful memory requirements, and networking constraints that make traditional microservice patterns unsuitable for fast, multiplayer game servers.
Game servers often avoid microservice architectures because real‑time communication, low latency, and stateful processing demand tightly coupled, high‑performance designs, making the added network overhead, stateless constraints, and complexity of microservices unsuitable for fast‑paced multiplayer games.
This article details the technical design and implementation of a CSS‑based countdown timer, component‑driven multi‑platform development, and a high‑concurrency real‑time interaction system using WeChat Cloud Development's watch API for Tencent Games' 2020 online conference.
This guide shows how to install and use nload, iftop, and sar for real‑time network traffic monitoring on Linux, explains each tool's key parameters, and provides two custom shell scripts that calculate per‑second inbound and outbound traffic using /proc/net/dev.
This article explains how FunTouTiao builds a high‑performance real‑time analytics pipeline using Flink, Hive, and ClickHouse, covering business scenarios, hour‑level and second‑level Flink‑to‑Hive architectures, streaming file sink mechanics, multi‑user permissions, ClickHouse performance tricks, and future roadmap for unified stream‑batch storage.
This article details Shopee Singapore Data Team’s implementation of a Flink‑based real‑time data warehouse, covering background challenges, layered architecture integrating Kafka, HBase, Druid, Hive, streaming pipelines, job management, monitoring, and future plans to expand Flink SQL support.
This article provides a comprehensive overview of process and thread scheduling in operating systems, explaining the role of the scheduler, different scheduling algorithms such as FCFS, SJF, round‑robin, priority, multilevel‑queue and lottery, their classification for batch, interactive and real‑time environments, and the key performance goals like fairness, throughput and response time.
The article presents a pure front‑end Complex Event Processing framework that captures user actions, uses an NFA‑based engine to evaluate dynamic strategies, synchronizes data across pages via local storage, and delivers millisecond‑level real‑time user reach on Mini‑program, Web, and Weex platforms.
This guide explains how to configure Laravel's broadcasting system, choose drivers like Pusher, Redis, or Socket.IO, implement event classes, set up channel authorization, and listen for real‑time updates in JavaScript using Laravel Echo for seamless WebSocket communication.
This article explains how Apache Flink's flexible state management can be leveraged to solve data correlation challenges in real‑time recommendation platforms, compares Flink with Spark and Storm, describes the underlying broadcast and managed state mechanisms, and provides a step‑by‑step implementation using Kafka, Druid, and custom broadcast functions.
This article examines the challenges of maintaining separate offline and real‑time data warehouses, explains the three‑layer ODS‑DW‑ADS model, evaluates the traditional Lambda architecture, and explores how a unified Flink stack with Kafka, HiveCatalog and streaming sinks can simplify metadata, SQL development, data import/export, and stateful processing for both batch and streaming workloads.
The article explains Huajiao's server‑and‑H5 driven dynamic layout architecture for multi‑user voice rooms, detailing its design principles, benefits, three core concepts, synchronization mechanisms, interaction flow, and how it drastically reduces client development effort while supporting flexible, real‑time UI changes.
This article explains how to develop a real‑time TopN ranking feature using Apache Flink, covering both global and grouped TopN implementations, nested TopN strategies, and provides complete Java code snippets for environment setup, word counting, windowing, and custom TopN functions.
Anime4K is a GPU‑accelerated super‑resolution algorithm tailored for animated images that achieves single‑digit millisecond latency, and the article explains its underlying residual‑based principle, practical results, and performance limitations on both GPU and CPU platforms.
Anime4K is a GPU-accelerated super‑resolution algorithm designed for animated images, achieving sub‑10 ms latency by enhancing low‑resolution frames with edge‑sharpened residuals, and the article details its principles, visual results, and real‑time performance limitations on typical CPUs.
This tutorial explains how to create a highly scalable, fault‑tolerant real‑time data processing platform by configuring a Kafka topic, a Cassandra keyspace, adding Spark and connector dependencies, developing a Java‑based Spark Streaming pipeline, enabling checkpoints, and deploying the application with spark‑submit.
Alibaba’s 20‑year anniversary event showcased a cloud‑enabled IoT wristband equipped with 102 full‑color LEDs, real‑time sensors and a high‑density wireless network that synchronized over 60,000 devices, delivering dynamic lighting, personalized guidance, interactive games, and large‑scale live video, illustrating the challenges and solutions of massive real‑time IoT deployments.
This article examines the surge in real‑time data demands for e‑commerce promotions, outlines how to collect, compute, and deliver streaming data, compares batch and stream processing, lists typical use cases, and discusses the challenges of building scalable, low‑latency pipelines.
This article explains how Meituan‑Dianping built the CAT platform to provide both user‑side and server‑side real‑time monitoring at trillion‑event scale, detailing its metrics, architecture evolution, storage strategies, and open‑source contributions.
This article shares JD's e‑commerce recommendation system practice, covering the overall online/offline architecture, recall and ranking modules, real‑time feature and model updates, multi‑objective and diversity strategies, first‑stage index‑based ranking, KNN recall, and a layered experiment platform for rapid iteration.
This article explains why the author chose Apache Flink for real‑time stream processing, highlighting its unique combination of high throughput, low latency, event‑time support, stateful computation, flexible windows, and fault tolerance, while also reflecting on the challenges of adopting a less‑documented technology.
Xianyu IFTTT is a scalable real-time user-relationship platform that enriches metadata, enables bidirectional buyer-seller interactions, integrates quickly via SLS logs, uses a chain-of-responsibility for customizable lists, processes push actions with fatigue filtering, and stores TB-scale data in Lindorm, delivering billions of daily records and more than double the click-through rate of offline pushes.
Xianyu’s Mach system tackles the e‑commerce challenge of instantly selecting high‑quality items from billions of products by leveraging Blink’s low‑latency stream computing, detailing its architecture—including state, windows, custom UDX functions, data merging, rule execution, and SQL‑to‑MVEL conversion—to achieve sub‑second processing at massive scale.
Meituan‑Dianping’s open‑source CAT is a high‑availability, real‑time distributed monitoring platform that now supports Java, C/C++, Python, Node.js and Go, processes billions of messages daily, offers scalable architecture, binary protocol, sampling aggregation, and is expanding its UI, stack and community.
This article examines the shortcomings of a legacy log‑collection setup, introduces a streamlined real‑time architecture that eliminates per‑machine Hadoop clients, centralizes configuration via Etcd with a web UI, and details the Go implementation—including configuration design, Etcd watching, Kafka integration, tail management, and per‑second rate limiting—complete with code snippets and performance graphs.
This article describes the shortcomings of a legacy log‑collection architecture, proposes a streamlined real‑time design that centralises configuration in Etcd, uses a single Go‑based logagent to tail files, applies per‑service rate limiting, and forwards logs to Kafka for downstream processing.
When high service reliability demands immediate detection of slow requests, this guide shows three Python techniques—using tail via subprocess, file.tell/seek loops, and a generator with yield—to continuously watch log files and trigger alerts as soon as specified patterns appear.
This article reviews the evolution of recommendation system architecture for C2C e‑commerce platforms, tracing stages from simple offline‑online pipelines through granular feed‑flow improvements, real‑time processing, and machine‑learning‑driven models, while highlighting user‑profile construction, challenges, and best‑practice guidelines.
This article explains how to design a distributed backend that ingests millions of clicks per second, stores data with Kafka and HDFS, computes top‑N articles using sliding windows and periodic aggregation, handles node failures, and mitigates click fraud, all while balancing accuracy and resource usage.
The article describes Overwatch, a distributed monitoring system developed by Dada‑JD Daojia that collects, aggregates, and visualizes RPC traffic in real time using consumer‑side agents, Kafka, Storm, and a Node.js CQRS architecture, enabling engineers to quickly locate and resolve service failures.
This article details the architecture and practical techniques behind WeChat's large‑scale monitoring system, covering lightweight data collection, classification of real‑time, non‑real‑time and user‑specific metrics, anomaly detection algorithms, automated configuration, and high‑performance storage solutions for billions of events per minute.
This article explains how Alibaba’s Sunfire monitoring platform processes terabytes of logs per minute, uses a pull‑based architecture with Brain‑Reduce‑Map roles, tackles scalability and reliability challenges, and outlines future directions such as MQL standardization and intelligent baselines.
Overwatch is an open‑source distributed monitoring platform built by Dada‑Jingdong Home that collects, aggregates, and visualizes RPC traffic across thousands of micro‑services in real time, enabling engineers to quickly pinpoint the root cause of system failures using directed‑graph visualizations and CQRS‑based data queries.
This article explains the objectives of recommendation systems, outlines four recommendation approaches, dives into personalized recommendation architecture and core algorithms, and discusses practical challenges such as real‑time processing, cold‑start, diversity, content quality, and exploration‑exploitation trade‑offs.
This article explains the objectives of recommendation systems, compares popular recommendation approaches, details the components and algorithms of personalized recommendation pipelines, and discusses practical challenges such as real‑time processing, freshness, cold‑start, diversity, content quality, and surprise handling.
This article details Ctrip’s redesign of its real‑time user behavior service, covering the new architecture, data flow, use of Java, Kafka, Storm, Redis, and MySQL, and how it achieves high real‑time performance, availability, scalability, and fault‑tolerance to support massive travel‑industry traffic.
This article explains how Redis-ML enables real‑time machine learning by extending Redis with modules, covering its architecture, random‑forest inference, performance benchmarks against Spark, and a complete movie‑recommendation use case with Docker, Scala, and Python examples.
Server-Sent Events (SSE) provide a lightweight, HTTP‑based mechanism for real‑time server push, and this article explains its principles, compatibility, and step‑by‑step implementation—including a simple server that streams timestamps every second and a front‑end page that displays the incoming data.
The article describes how Ctrip rebuilt its real‑time user behavior platform using a Java‑based stack (Kafka, Storm, Redis, MySQL) to achieve millisecond‑level latency, high availability, scalable performance, and robust handling of traffic spikes, failures, and data back‑pressure.
The Sentinel system was built to provide real‑time, zero‑modification monitoring of airline ticket business services by consuming Tianwang logs through a Storm cluster, offering flexible rule configuration, addressing performance pitfalls, and planning future enhancements such as custom monitoring scripts and visual dashboards.
Learn how to construct a simple, high‑availability real‑time stream processing platform using lightweight components such as Kafka, Zookeeper, Thrift/Avro, and optional storage like MongoDB or Elasticsearch, offering a practical alternative to heavyweight frameworks like Storm and Spark Streaming for small‑to‑medium enterprises.
Alibaba’s SunFire platform delivers massive‑scale, real‑time log collection, processing, and visualization for e‑commerce spikes like Double 11, using low‑overhead agents, asynchronous Map/Reduce pipelines, fault‑tolerant task scheduling, and shared inputs to ensure accurate, low‑latency monitoring across billions of transactions.
The article introduces QReport, a front‑end‑focused real‑time data reporting system developed to overcome the limitations of the Beacon log‑analysis platform, detailing its architecture, page‑identification method, flow analysis, real‑time capabilities, richer metrics, and overall advantages for web analytics.
The article outlines the end‑to‑end workflow of H5 live streaming, discusses state control, WebSocket‑based comment handling, heartbeat reconnection, video compatibility issues, and practical code techniques for detecting and recovering from stream stalls.
The CAT real‑time monitoring system, open‑sourced in 2014 for Java applications, combines a lightweight ThreadLocal‑based client SDK, Netty‑driven asynchronous transport, and a highly scalable backend that processes ~100 TB of logs daily across 70 machines, using custom binary serialization, in‑memory modeling, segmented storage with 48‑bit indexing, and hourly aggregation to provide near‑full‑volume fault detection, localization, and performance analysis.
The article describes how YHD's precision recommendation team built a real‑time, highly available, traceable general recommendation platform, detailing its background, overall architecture, visual configuration and traceability subsystems, and reporting significant improvements in development speed, reuse and user satisfaction.
This article provides a comprehensive overview of the Zephyr real‑time operating system, detailing its Linux‑Foundation‑led community structure, website navigation, core features, modular architecture, development guides, and the organizational model that supports its rapid evolution in the IoT space.
This guide explains how to enable Alibaba Cloud Data Transmission Service (DTS) with the dts-ads-writer plugin to continuously synchronize changes from an RDS for MySQL instance to a real‑time write table in an analytic database, covering prerequisites, configuration, and monitoring steps.
This article explains the difference between unreliable (1‑31) and reliable real‑time (32‑64) Linux signals, demonstrates the behavior with two C programs, and reveals the kernel data structures and limits that govern signal queuing and delivery.
This article provides a concise overview of several open‑source real‑time stream processing platforms—including S4, Storm, StreamBase, HStreaming, Esper/NEsper, Kafka, Scribe, and Flume—highlighting their primary features, programming languages, and project links for future technical research.
This article explains the concepts of nice and priority values in Linux, how they differ, their impact on process scheduling, and compares historic O(1) and modern CFS schedulers, including real‑time scheduling policies, providing practical command examples for administrators.
This article outlines a reference architecture for a low‑latency, horizontally scalable real‑time stock prediction system built with open‑source components such as Spring Cloud Data Flow, Apache Geode, Spark MLlib, and Hadoop, and discusses data flow steps, simplified deployment, and algorithm choices for market forecasting.
This article details the design and implementation of 58’s real‑time messaging platform, covering its business background, overall architecture, protocol design for extensibility and debugging, and solutions for fast TCP reconnection to ensure stable, high‑throughput delivery for intra‑city freight services.
This article shares the author's practical experience building a real‑time log analysis platform at Sina, covering service scope, ELK architecture, performance optimizations, usability improvements, new features, common pitfalls, and a concise Q&A for engineers handling massive log streams.
The article presents an open‑source, highly scalable reference architecture that combines real‑time data ingestion, machine‑learning model training, and low‑latency prediction using components such as Spring Cloud Data Flow, Apache Geode, Spark MLlib, and Hadoop to enable continuous stock price forecasting.
This article presents a detailed walkthrough of Meizu’s real‑time push platform, covering its four‑layer architecture, high‑concurrency design, micro‑service RPC framework, power‑saving strategies, duplicate‑message handling, DNS reliability, load‑balancing tactics, monitoring setup, and gray‑release deployment.
The article explains the publish‑subscribe (pub/sub) messaging model, its time, space, and synchronization decoupling features, typical real‑time scenarios such as chat and log processing, and details how Redis implements pub/sub through channels and pattern subscriptions, including command syntax and internal data structures.
This article reviews various web real‑time message push techniques—including polling, long‑polling, iframe streaming, socket plugins, and WebSocket—evaluates their pros and cons, and explains why the author selected the Comet approach implemented with the Python Tornado framework for a web push system.
This article explains what Meteor is, its full‑stack Node.js/MongoDB architecture, real‑time data handling with DDP, and the reasons it dramatically speeds up web and mobile app development for startups and rapid prototyping.
This article provides a concise overview of several open‑source real‑time stream processing platforms—including S4, Storm, StreamBase, HStreaming, Esper/NEsper, Kafka, Scribe, and Flume—highlighting their main features, programming languages, and project links for further reference.
