Knowledge Planet: Old Dock's Tech Chronicles Zhihu: SamDeepThinking A technical manager who still codes heavily on the front line. From junior developer to tech lead, then tech manager, now leading the whole front‑ and back‑end development team—leveling up along the way. I have some insights on programming, career development, and tech management.
The article explains why sharding should be a last‑resort scaling option, describes vertical and horizontal partitioning, compares hash, range and directory sharding schemes, discusses hotspots, routing, data colocation, migration steps and tool choices, and warns about the operational complexity involved.
The article explains why the three‑decade‑old multipart/form-data format remains the standard for HTTP file uploads, detailing its encoding rules, how it differs from application/x-www-form-urlencoded, the structure of multipart requests, server‑side processing advantages, and why newer alternatives have not replaced it.
The article argues that code age or outdated technology alone doesn't define legacy code; instead, when product requirements evolve and the old code must be repeatedly patched, it becomes legacy, while unchanged requirements allow even decade‑old code to remain good.
The article uses a same‑city flash‑delivery story to walk through how HTTPS protects confidentiality, integrity, and authenticity by comparing symmetric and asymmetric encryption, key exchange, and the role of certificate authorities in establishing trust.
The article recounts how a C++‑based real‑time inventory system on 30 machines was forced to reboot nightly to free memory, illustrating the pitfalls of manual memory management and arguing that languages offering safer resource handling improve developer productivity and reduce error‑prone code.
The article walks through a production scenario where business documents must be synchronized to a low‑code platform via its OpenAPI, explaining how to build a unified client, verify apparent failures, apply a single retry, and fall back to a task table for asynchronous recovery, all illustrated with concrete code.
The article explains how to judge code quality by focusing on stability—handling exceptions, retries, and alerts—and clarity—organizing logic into readable, maintainable steps—illustrated with a real‑world document‑sync example and simple function patterns.
When traffic spikes, a multi‑table JOIN can hold database connections far longer than separate single‑table queries, quickly exhausting the connection pool and slowing the entire system, as demonstrated by concrete timing examples and a practical workaround.
The article explains that observability goes beyond simple monitoring by combining metrics, logs, and traces to pinpoint where and why a system issue occurs, especially in microservice and cloud‑native environments, and stresses the importance of correlating data rather than merely collecting more.
This article presents a detailed technical blueprint for building an enterprise‑grade single sign‑on system that combines Apereo CAS, OAuth2, and JWT across four microservices, covering service responsibilities, data models, API contracts, deployment trade‑offs, and operational safeguards.
