Tagged articles
Stateless Services
15 articles · Page 1 of 1
This article explains how RocketMQ LiteTopic solves the task state persistence problem for stateless MCP services by assigning each task a dedicated message channel that acts as an ordered, durable ledger, enabling reliable task tracking, automatic retries, and seamless replica failover without violating the protocol's stateless requirement.
AI AgentLiteTopicMCP
0 likes · 11 min read

The article explains how to build highly available stateless services by using redundant deployment, vertical and horizontal scaling, appropriate load‑balancing algorithms, monitoring, and automated recovery, and also discusses high‑concurrency identification, CDN/OSS usage, and practical recommendations for cloud‑native environments.
High AvailabilityHorizontal ScalingStateless Services
0 likes · 11 min read

This article explains the AKF scalability cube for microservice architecture, detailing the Y‑axis functional decomposition, X‑axis horizontal scaling, Z‑axis data partitioning, as well as front‑end/back‑end separation, stateless services, and RESTful communication, providing practical diagrams and guidance for building robust, scalable systems.
Data PartitioningRESTfulStateless Services
0 likes · 9 min read

This article explains how to achieve high availability for stateless services by employing redundancy, vertical and horizontal scaling, various load‑balancing algorithms (random, round‑robin, weighted, least‑connections, source‑hash), and automatic scaling techniques in cloud‑native environments, while also covering performance monitoring and CDN/OSS usage.
Auto ScalingHigh AvailabilityHorizontal Scaling
0 likes · 10 min read

This article explains how to build highly available stateless services by using redundant deployment, vertical and horizontal scaling, various load‑balancing algorithms, and automatic recovery mechanisms, while also covering monitoring, high‑concurrency identification, and the role of CDN and OSS in resilient architecture.
CDNHigh AvailabilityOSS
0 likes · 10 min read

This article explains how to build highly available stateless services by covering redundant deployment, load‑balancing algorithms, vertical and horizontal scaling, CDN/OSS usage, and practical recommendations for monitoring, automated recovery, and minimizing failure impact.
High AvailabilityStateless Servicescloud native
0 likes · 13 min read

The article outlines the evolution of microservice architecture, its advantages, four concrete design principles—including AKF splitting, front‑end/back‑end separation, stateless services, and RESTful communication—while also discussing common challenges and practical mitigation strategies.
Design PrinciplesRESTful APIStateless Services
0 likes · 10 min read

This article outlines ten crucial design principles for building robust microservice systems, covering API gateways, stateless services, database scaling, caching, service splitting, orchestration, configuration management, logging, resilience patterns, and comprehensive monitoring to ensure high performance and reliability.
API gatewayCircuit BreakerStateless Services
0 likes · 12 min read

This article outlines ten crucial design principles for building robust microservice systems, covering API gateways, stateless services, database scaling, caching strategies, service decomposition, orchestration, configuration management, logging, fault tolerance, and comprehensive monitoring, each illustrated with clear diagrams.
API gatewayCachingStateless Services
0 likes · 11 min read

The article explains the historical background, core characteristics such as scalability, cost‑efficiency, fault tolerance, and elasticity, and outlines essential design principles for distributed systems, emphasizing low hardware requirements, horizontal scaling, avoidance of single points of failure, reduced communication overhead, and stateless services.
Horizontal ScalingStateless Servicesfault tolerance
0 likes · 12 min read

This article explains practical techniques for designing high‑availability and scalable systems—covering entry, business, cache, and database layers—so developers can handle rapid user growth without service interruptions or degraded performance.
CachingDatabase ReplicationStateless Services
0 likes · 13 min read

Distributed systems, long used since the 1970s and popularized by internet giants like Google, offer scalable, cost‑effective, and fault‑tolerant architectures by leveraging many low‑cost servers, emphasizing horizontal scaling, avoidance of single points of failure, minimal inter‑node communication, and stateless services for elastic application deployment.
Horizontal ScalingStateless Servicesdistributed systems
0 likes · 13 min read

This article explains practical techniques for designing high‑availability and scalable systems by addressing entry, business, cache, and database layers, offering concrete solutions such as keepalived, stateless services, cache partitioning, and replication strategies to handle rapid user growth without service disruption.
Stateless Servicescache partitioningdatabase-replication
0 likes · 11 min read

This article, distilled from a lively discussion in the InfoQ High‑Efficiency Operations group, outlines a modular “building‑block” approach to operations automation, presents core methodologies, explains why automation tools exist, compares Puppet, SaltStack, and Ansible, and offers practical guidance for selecting and implementing automation solutions.
CI/CDOperations AutomationStateless Services
0 likes · 11 min read

The article explains the origins, core features such as scalability, cost‑effectiveness, fault tolerance, and elastic expansion of distributed systems, and outlines design philosophies like low hardware requirements, horizontal scaling, avoidance of single points of failure, minimized inter‑node communication, and stateless service architecture.
Horizontal ScalingStateless Servicesdistributed systems
0 likes · 11 min read
