Engineering notes for cloud native systems, middleware, observability, and AI infrastructure.
stellhub/blog is the English technical writing repository for StellHub.
This repository is designed for long-form engineering articles, architecture notes, technical research, and practical implementation guides. The writing style focuses on production experience, system design trade-offs, and implementation details that are useful for engineers building real distributed systems.
StellHub is not just a blog name. It is a technical notebook for building reliable, observable, and scalable infrastructure.
Join GitHub Discussions to propose article ideas, ask technical questions, and discuss cloud-native systems, middleware, observability, reliability engineering, performance optimization, and AI infrastructure.
Recommended discussion directions are maintained in DISCUSSIONS.md.
This blog mainly focuses on the following areas:
| Area | What it covers |
|---|---|
| Cloud Native | Kubernetes, containers, deployment models, service runtime, infrastructure automation |
| Microservices | service governance, naming models, routing, rate limiting, retry, timeout, circuit breaking |
| Middleware | registry, configuration center, message queue, gateway, distributed coordination, storage design |
| Observability | metrics, logs, traces, OpenTelemetry, Prometheus, Grafana, Tempo, SLI/SLO/SLA |
| Reliability Engineering | SRE practices, failure handling, capacity planning, incident analysis, production resilience |
| Network & Performance | zero-copy, batching, pipeline, serialization, connection management, throughput optimization |
| AI Infrastructure | LLM gateway, agent runtime, model serving, AI-native middleware, engineering practices |
Good technical writing should not stop at definitions. It should answer:
- Why does this problem exist?
- How do mature engineering systems solve it?
- What are the trade-offs behind each solution?
- How can it be implemented in real projects?
- What should be avoided in production?
The articles in this repository are expected to be opinionated, practical, and architecture-driven.
A typical article may follow this structure:
articles/
cloud-native/
microservices/
middleware/
observability/
reliability/
performance/
ai-infrastructure/
assets/
covers/
diagrams/
README.md
Suggested article format:
# Article Title
## Background
## Problem Statement
## Core Concepts
## Architecture Design
## Implementation Details
## Production Best Practices
## Common Pitfalls
## Summary
## ReferencesPlanned and ongoing writing directions include:
- Microservice observability standards in the cloud native era
- Retry strategy best practices in software development
- StellHub microservice observability specification
- Five-level naming model for large-scale enterprise microservices
- Layered governance and troubleshooting of network timeouts
- Cross-language distributed tracing research for large enterprises
- End-to-end throughput optimization with batching, sequential I/O, zero-copy, pipelining, and reduced serialization
- Middleware Site Reliability Engineering based on SLI, SLO, and SLA
The Chinese technical writing repository is available here:
Some articles may have both English and Chinese versions, but the two repositories are not required to be exact mirrors. The English repository focuses more on international technical communication, while the Chinese repository focuses more on deep engineering explanation and local developer readability.
- Be precise, not vague.
- Be practical, not decorative.
- Explain trade-offs, not just conclusions.
- Prefer architecture diagrams and reproducible examples.
- Cite authoritative sources when discussing standards, protocols, or official behavior.
- Keep articles useful for engineers who need to design, debug, and operate real systems.
- Build a stable article taxonomy
- Add cover images and architecture diagrams
- Add English versions of core technical essays
- Add references and reading lists for each topic
- Publish selected articles to the official StellHub website
Follow the StellHub WeChat official account for deep technical articles about cloud-native systems, middleware, microservices governance, observability, reliability engineering, performance optimization, and AI infrastructure.
The license has not been finalized yet.
Before reusing, translating, or redistributing the content, please check the repository license once it is added.
StellHub · Engineering the invisible infrastructure behind modern software