0 views collected around this technical thread.
This article explains a metadata‑driven approach for extending massive tables—using a separate extension table, sharding, and Elasticsearch sync—to add new fields to billion‑row databases without locking the primary table or disrupting online services.
This article examines why storing 2 billion phone numbers using INT or BIGINT is problematic and argues for using VARCHAR(20) to preserve data integrity, support international formats, simplify queries, and avoid common pitfalls in database design and development.
This article explains how to migrate sharded Mycat data to ActionDB with ActionOMS, addressing duplicate primary keys by modifying both source and target schemas, configuring migration tools, and completing validation and post‑migration steps.
While MySQL 5.7 native DDL methods (copy, inplace rebuild, index build, metadata‑only) vary in speed, space use, lock impact, and binlog output, GH‑OST consistently offers the fastest execution, lowest lock blocking, real‑time replication, albeit at roughly double storage cost, making it ideal for risk‑averse online schema changes.
This article introduces a free, low‑code tool that lets backend developers automatically generate functional front‑end management pages from database structures or description files, detailing two generation methods, configuration steps, code snippets, and deployment tips.
This article explains three relatively new MySQL 8.0 features—hidden (invisible) columns, generated invisible primary keys, and invisible indexes—detailing their purpose, how to create and use them, and practical scenarios where they can help avoid schema‑change issues or test query performance.
This article outlines a comprehensive approach to building a scalable multi‑account login system that supports phone‑number/password, phone‑number/verification‑code, and various third‑party OAuth providers, detailing workflow steps, database schema, advantages, drawbacks, and a one‑click login integration.
This article walks through the Mall project's product module—covering its architecture, feature design, database schema, and API implementation—while providing links to source code, video tutorials, and a mind‑map that together serve as a comprehensive guide for building robust e‑commerce systems.
This article details the design and implementation of a coupon system for a rental platform, covering business flow, database schema, backend services, caching strategies, state management, and future optimization directions to ensure reliable coupon distribution and redemption.
This article explains the end‑to‑end design of a coupon system for e‑commerce, covering promotion types, core workflows, service architecture, database schema, distributed transaction handling, scaling strategies, rate limiting, and consistency mechanisms such as TCC.
This article explains the concepts of data model, data dictionary, database schema, and ER diagram, clarifies their differences, and compares them across stages, purposes, detail levels, authors, users, tools, and forms to help readers grasp database design terminology.
This article provides a comprehensive walkthrough of the coupon feature's database tables—including definitions for coupons, coupon history, product relations, and category relations—along with screenshots of both admin and mobile interfaces that illustrate how these tables are used in an e‑commerce system.
This article provides a comprehensive walkthrough of the order return and return‑reason database tables, detailing each field, status codes, and the corresponding admin and mobile UI screens that illustrate how the return process works in an e‑commerce system.
This article dissects the e‑commerce shopping cart database schema, explains the end‑to‑end order lifecycle—from adding items and calculating promotions to generating confirmation orders, creating orders, and handling cancellations—while highlighting key implementation details and code references for backend developers.