This article investigates the meaning of the number in parentheses for MySQL INT types, demonstrates through storage tests that INT(4) and INT(11) have identical storage size and range, and explains how the ZEROFILL attribute changes only the displayed width.
This article summarizes comprehensive MySQL index design guidelines, covering naming conventions, column selection criteria, index count control, handling of frequently updated columns, function and duplicate indexes, small‑table considerations, and index ordering to optimize query performance.
This article walks you through using Navicat for MySQL to create databases and tables, design table structures, and perform native SQL SELECT queries—including filtering, multiple conditions, and column selection—illustrated with step‑by‑step screenshots and code examples.
This article explains practical principles for designing scalable, stateless backend systems—choosing the right tools, using multiple servers, caching, rate limiting, dividing responsibilities, handling large data volumes, and providing concrete example architectures for projects of any size.
Starting with MySQL 8.0.23, columns can be marked INVISIBLE, causing them to be omitted from SELECT * queries unless explicitly referenced; this article explains the feature, demonstrates creation, inspection, DML considerations, schema modifications, backup behavior, and its impact on database design.
This article explains why data warehouses are critical for decision‑making, outlines the challenges of immature warehouses, and provides a step‑by‑step framework—including goal setting, technology selection, problem identification, domain modeling, layer design, modeling principles, and governance standards—to help teams build a robust, maintainable data warehouse.
This article outlines practical approaches for implementing multi‑account login, covering early‑stage username/password and phone‑based registration, detailed authentication flows, OAuth2 integration with third‑party providers, and comprehensive database schema designs to unify local and external user identities.
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 presents an extensive collection of MySQL performance‑tuning techniques, covering index design, query rewriting, use of UNION and EXISTS, temporary tables, NOLOCK hints, join limits, backup strategies, storage engine choices, data‑type selection, and other practical tips to improve query efficiency and overall database reliability.
This article explains the concept, technical solutions, workflow diagrams, and database schema for implementing unified multi‑account login using username/password, mobile verification, and third‑party OAuth2 integrations, providing practical design guidance without detailed source code.
This article explains why setting MySQL columns to NOT NULL improves query optimization, reduces index complexity, saves storage space, and prevents unexpected behavior in calculations, while also detailing default values, handling of NULL in aggregates, and the internal row format differences between NULLable and NOT NULL columns.
This article explains why defining columns as NOT NULL in MySQL improves query optimization, reduces index complexity and storage overhead, and avoids unexpected behavior in aggregates and calculations, while also covering default values, row formats, and practical testing results.
This article outlines ten practical MySQL development guidelines—from always using InnoDB and simple data types to avoiding SELECT *, ENUM, and low‑cardinality indexes, while emphasizing proper naming, charset choices, NOT NULL constraints, and continuous SQL monitoring with Percona Toolkit.
This article outlines ten practical MySQL development guidelines—from using InnoDB tables and simple data types to avoiding SELECT * and unnecessary ENUMs—helping DBAs and developers collaborate more efficiently and write cleaner, faster SQL.
This article compiles a comprehensive set of MySQL interview questions covering index structures, B‑tree vs. hash trade‑offs, primary‑key and clustered‑index design, ACID properties, isolation levels, lock types, storage‑engine choices, data‑type considerations, binlog formats, pagination strategies, sharding, stored procedures, normalization, and MyBatis parameter syntax.
This article explains how Vivo designed a company‑wide comment middle‑platform, chose MySQL and MongoDB, deep‑dived into MongoDB cluster architecture, shard key strategies, and practical solutions for scaling, migration, and high availability in a high‑traffic environment.
This article explains MySQL AUTO_INCREMENT behavior, demonstrates creating tables with unsigned int primary keys, shows how to set and inspect the AUTO_INCREMENT value, discusses its maximum limits, and recommends using bigint or explicit primary keys to avoid overflow and duplicate‑key errors.
This article details Vivo's journey in building a company‑wide comment platform, explaining why MongoDB was chosen over MySQL, how its sharded cluster is structured, the challenges of shard‑key selection, and the practical steps taken to scale and maintain the system.
This article explains how MySQL treats NULL values, why columns defined with NULL can invalidate indexes, demonstrates the behavior of IS NULL, IS NOT NULL, the spaceship operator, IFNULL, COUNT, DISTINCT, GROUP BY and ORDER BY with NULLs, and offers practical recommendations for schema design.
This article explains the definitions of domain and data models, illustrates why they are often confused, shows real‑world examples of misusing each, and provides practical guidance on separating them to improve system design, scalability, and maintainability.
This article explores the key challenges of designing a flash‑sale (秒杀) system—such as overselling, high concurrency, request flooding, and database strain—and presents a comprehensive backend architecture with database design, dynamic URLs, caching, rate limiting, async ordering, and service degradation techniques.
This article presents a comprehensive set of mandatory and recommended conventions for MySQL table creation, SQL writing, and index design, aiming to improve backend development efficiency, reduce erroneous DDL and queries, and enhance overall database performance.
The article explains the concept and requirements of primary keys in MySQL, outlines best practices such as avoiding updates and reuse, and discusses how primary keys serve as clustered indexes in InnoDB, highlighting the performance advantages of using business‑agnostic auto‑increment IDs over random keys.
This article explores practical approaches to building extensible business systems by addressing database scalability through sharding and partitioning, designing flexible application layers with configurable rules and hooks, and applying SOA principles to achieve modular, service‑oriented architectures that adapt to changing requirements.
This comprehensive guide answers the most frequent MySQL interview questions, covering index structures, transaction isolation levels, table design best practices, storage engine differences, query optimization techniques, and miscellaneous topics such as data types, binlog formats, and sharding strategies.
In this presentation, JD Intelligent Cloud architect Ge Jibin walks through the technical architecture, deployment strategies, performance tuning, and real‑world use cases of the TiDB cloud database, providing a comprehensive slide deck for developers and engineers.
This guide outlines comprehensive MySQL best‑practice standards covering naming conventions, storage engine selection, charset usage, table and column comments, size limits, partitioning, hot‑cold data separation, index design, SQL coding rules, and operational safeguards to ensure performant, maintainable, and secure database systems.
This article presents a comprehensive set of mandatory and recommended MySQL database standards—including table creation rules, SQL writing conventions, and index design practices—aimed at preventing improper schemas, reducing erroneous queries, and improving overall performance for backend development teams.
This article outlines essential database design concepts, covering the relationship between source documents and entities, primary‑foreign key design, basic table characteristics, normalization standards, handling many‑to‑many relationships, primary key strategies, data redundancy, ER‑diagram considerations, view usage, and performance‑boosting techniques.
This article examines common MySQL pitfalls—including signed vs. unsigned integers, auto‑increment key requirements, varchar length versus byte count, case‑insensitive collations, and storing emoji characters—providing concrete SQL examples, error screenshots, and configuration tips to help developers avoid unexpected errors.
MongoDB’s flexible, schema‑less design offers performance benefits but can become a maintenance nightmare as projects grow, so the article explains why introducing external schema protocols like Google’s Protobuf or Facebook’s Thrift provides structure, reduces bugs, and balances flexibility with robustness.
This article presents a comprehensive MySQL database standard covering table creation rules, SQL writing conventions, and index design recommendations, explaining the rationale behind each mandatory or suggested practice to improve performance, maintainability, and consistency across projects.
This article presents a curated list of 100 essential MySQL interview questions covering indexes, transaction fundamentals, storage engine differences, table design, query optimization, and common pitfalls, providing concise explanations and practical examples to deepen developers’ understanding and prepare them for technical interviews.
The article examines the difficulties of reusing SQL Server stored procedures to obtain simple boolean checks, illustrates a concrete example of counting jobs with temporary tables, discusses maintenance pitfalls, and concludes that business logic is often better implemented outside stored procedures.
This article explains the design philosophy of relational databases, describing the relational model, its components, and how SQL operates as a set‑oriented language with examples of SELECT, GROUP BY, UNION, JOIN and basic DML statements.
This article examines MySQL's recommendation to use auto_increment primary keys instead of UUID or Snowflake IDs by creating three tables, running insertion benchmarks with Spring Boot, comparing index structures, and discussing the performance trade‑offs and practical drawbacks of each approach.
This article explains the technical solutions for unified multi‑account login in web applications, covering early‑stage username/password and mobile verification flows, detailed process steps, OAuth2.0 third‑party integration, and comprehensive database schema design for local and third‑party user authentication.
This article provides a comprehensive interview‑style overview of MySQL fundamentals, covering relational database concepts, data types, storage engines, SQL syntax, version checking, normal forms, views, stored procedures, and performance tips, all essential for backend developers and database professionals.
The article explains why using NULL columns in MySQL can lead to extra storage, index complications, query errors, and performance degradation, and provides concrete examples and best‑practice recommendations to prefer NOT NULL constraints whenever possible.
This article explains how to design database schemas and choose between MySQL and Redis for handling likes, comments, and bookmark features in mobile applications, covering requirements, schema examples, query patterns, scaling challenges, and data consistency considerations.
This article presents a comprehensive guide to database design, covering the relationship between source documents and entities, primary and foreign keys, table properties, normalization standards, handling many‑to‑many relationships, key selection, data redundancy, ER diagram considerations, view usage, intermediate and temporary tables, integrity constraints, the "Three‑Few" principle, and practical techniques for improving database performance.
This article explores key database design decisions—including the benefits and drawbacks of auto‑increment primary keys, the trade‑offs of redundant columns, optimal index counts, and when to choose VARCHAR versus CHAR—offering practical guidelines to improve performance, storage efficiency, and maintainability.
This article explores the requirements and database design patterns for implementing likes, comments, and favorites in apps, comparing traditional MySQL schemas with Redis‑based storage and caching solutions, and discusses their trade‑offs, scalability, and data consistency considerations.
This article explains the TPC‑C benchmark, covering its purpose, data model, database schema, the five transaction types, and a detailed step‑by‑step walkthrough of the New‑Order operation with accompanying SQL illustrations, while also summarizing workload characteristics and providing reference links.
This article explains the database design for likes, comments, and favorites in apps, comparing MySQL table structures and Redis storage solutions, discussing query patterns, scalability challenges, and data consistency measures for moderate to massive traffic scenarios.
The article shares practical experiences on running test cases concurrently using Java multithreading and a custom thread pool, and outlines MySQL database naming, null handling, and schema design guidelines, including full code examples for the case runner and thread pool implementation.
This article explains why each microservice should own its own database, outlines four data‑sharing approaches, describes how to perform backward‑compatible schema changes, and introduces the Saga pattern for cross‑service transactions, providing practical guidance for building robust microservice architectures.
This guide outlines comprehensive MySQL best practices covering naming conventions, table engine and charset choices, field type selection, index design principles, common index column recommendations, ordering of composite indexes, avoidance of redundant and foreign‑key constraints, SQL development rules, and operational guidelines for large‑scale data handling.
This article explains the functional requirements for likes, comments, and favorites, compares MySQL and Redis storage solutions, provides schema and command examples, discusses their advantages and drawbacks, and offers guidance on ensuring data consistency for scalable app back‑ends.
This article explains what foreign keys are, how they enforce referential integrity in relational databases, the different actions (RESTRICT, CASCADE, SET NULL), their performance overhead demonstrated by benchmarks, and practical guidelines for simulating or using foreign keys in high‑concurrency applications.
This article examines the functional requirements for likes, comments, and favorites in apps and compares MySQL and Redis based database designs, discussing schemas, queries, scalability challenges, and consistency considerations for handling moderate to massive data volumes.
An engineer recounts a real‑world challenge of reusing existing SQL stored procedures to check a user's job, certification, and disclosure status, explores why inserting results into temporary tables can cause maintenance headaches, and concludes that moving business logic out of the database often yields cleaner, more maintainable code.
This article examines the purpose, benefits, and drawbacks of MySQL foreign keys, presents various usage scenarios with performance tests, discusses constraints, and offers guidance on when to apply or avoid foreign keys in database design.
The article examines the drawbacks of reusing stored procedures for business logic, illustrates maintenance challenges with example code, and argues that moving simple existence checks to the database while keeping complex logic in application code yields better readability, extensibility, and performance.
The article explains how to formally name data schemas, data structures, and data models, clarifies their relationships, introduces physical, business, logical, and deployment schemas, and proposes strategic and tactical schemas to improve data architecture and management across organizations.
This guide presents comprehensive MySQL best‑practice standards covering object naming, basic schema design, field definitions, index design, common index column recommendations, covering indexes, SET usage, SQL development rules, and safe operational behaviors to improve performance, maintainability, and security.
The article explains why MySQL's AUTO_INCREMENT primary keys can become non‑monotonic and non‑continuous due to early‑version in‑memory counters, restart behavior, concurrency lock modes, and how MySQL 8.0 persists the counter to mitigate these issues while discussing design trade‑offs and best practices.
This comprehensive guide outlines MySQL database naming conventions, basic design rules, field specifications, index design principles, common index recommendations, and best practices for SQL development and operational behavior to ensure performance, maintainability, and security.
This tutorial walks you through using Navicat 12 to design, relate, and export a database schema for a mall permission management module, covering model opening, table creation, foreign‑key setup, auto‑layout, SQL export, and reverse engineering with clear screenshots.
This article explains how to design a high‑performance, strongly consistent flash‑sale (秒杀) system using MySQL InnoDB, covering table schema, unique indexes, transaction handling, row‑level locking, and trade‑offs between consistency and performance, with concrete SQL examples and flow diagrams.
This article explains the programming mindset of splitting and merging, details MySQL partition implementation and internal file types, demonstrates how partitioning improves query performance, and explores sharding strategies, middleware choices, and common issues like distributed transactions and cross‑shard joins.
This article explains MySQL's large object data types—TEXT, BLOB, and JSON—covering their storage formats, performance implications, indexing rules, partition restrictions, relevant server parameters, and practical examples of creating tables, inserting data, and querying JSON values.
This article explains how to build a real‑time internet gold investment platform by outlining gold’s financial characteristics, identifying key participants, describing the three‑pillar system architecture, detailing buy, sell, withdraw and gift workflows, and presenting the necessary database tables for robust transaction and reconciliation management.
This article provides a comprehensive overview of MySQL data types—including numeric, floating‑point, decimal, string, date/time, binary, bit, enum, and set types—explaining their storage characteristics, appropriate use cases, and performance implications through practical examples and SQL demonstrations.
This article explains InnoDB's logical storage hierarchy—tablespace, segment, extent, page—then details MySQL partitioning concepts, types, example DDL, performance impacts, and best‑practice tips for OLTP and OLAP workloads.
Optimizing MySQL tables with tens of millions of rows requires a systematic approach that considers data volume, table type, and performance goals, and involves design standards, business‑layer tactics, architectural strategies, and database‑specific tweaks such as proper indexing, configuration, and management practices to maintain efficiency.
This guide presents comprehensive MySQL best‑practice rules covering object naming conventions, fundamental schema design, field type selection, index creation strategies, and SQL development habits to improve performance, maintainability, and reliability of production databases.
This article presents a thorough set of MySQL best‑practice guidelines covering object naming conventions, basic table design, column definitions, index creation, index usage policies, SQL coding standards, and operational behaviors to improve performance, maintainability, and data integrity.
This article explains the importance of good database design, walks through the stages of building an ER conceptual model, shows how to map entities, attributes, and relationships to relational schemas, and demonstrates how normalization (1NF, 2NF, 3NF, BCNF) improves schema quality using practical examples.
This article explains the concept of ER tables, demonstrates how they are configured and used in the DBLE middleware with parent‑child relationships, shows a practical SELECT example and query plan analysis, and concludes with best‑practice recommendations for leveraging foreign‑key optimizations.
The article explains why the Alibaba Java Development Manual restricts joins to three tables, discusses MySQL’s join algorithm limitations, and offers practical alternatives such as query decomposition, denormalization, and using IN or hash joins to improve performance.
This article explains the fundamentals of role‑based access control, introduces user groups and role groups for batch authorization, and provides a detailed data‑dictionary with database tables and diagrams to help developers design a flexible, extensible permission system for large applications.
This article explains the relationships between source documents and entities, the role of primary and foreign keys, the characteristics of base tables, normalization standards, handling many‑to‑many relationships, primary‑key generation methods, data redundancy concepts, ER‑diagram best practices, view usage, and performance‑optimizing techniques for relational databases.
This article explains the fundamentals of time‑series databases, introduces InfluxDB’s key components such as databases, measurements, retention policies, tags, fields, series, and points, describes the line protocol syntax, compares it with traditional databases, and outlines the design trade‑offs that shape its performance and limitations.
This article provides a comprehensive introduction to data warehouses, covering their definition, architectural layers, characteristics, modeling approaches such as Inmon and Kimball, fact and dimension table design, star and snowflake schemas, and best‑practice principles for building scalable, maintainable warehouse solutions in the big‑data ecosystem.
The article describes a stable withdrawal system that integrates UnionPay and WangLian, emphasizing immutable serial numbers, strict exception handling, real‑time monitoring, multi‑stage compensation, a database‑driven routing engine handling up to 500 k transactions per hour, and an operations console for manual recovery, while outlining future optimizations.
This guide compiles comprehensive MySQL conventions covering object naming, storage engine choices, character sets, table and column design, indexing strategies, query optimization, and operational safeguards to improve performance, maintainability, and data integrity in production environments.
The article explains how testers can improve software quality by actively reviewing API definitions, understanding system architecture, evaluating database designs, reading code, and mastering configuration files, turning testing from a final checkpoint into a proactive, integral part of the development lifecycle.
This article details the database table structures used for managing various homepage recommendation features—including brand, new product, popular product, subject, and advertisement tables—providing full MySQL DDL statements, field descriptions, and visual examples of both admin and mobile interfaces.
This guide outlines comprehensive MySQL design standards—including naming conventions, table structures, column types, indexing, partitioning, and SQL best practices—to help developers, DBAs, and QA engineers build stable, high‑performance databases for production environments.
This article explains the technical solutions, workflow diagrams, and database schema for building a multi‑account login system that supports username/password, phone‑number, and third‑party (e.g., QQ, WeChat) authentication, while outlining security measures such as password hashing, login throttling, and token management.
This article provides a detailed analysis of the order-related database tables—including orders, order items, operation history, and order settings—along with their fields, data types, and meanings, and showcases how these tables are presented in both admin and mobile interfaces of an e‑commerce system.
This article walks through the core database tables that power product editing, SKU management, tiered pricing, full‑reduction discounts, member pricing, product reviews, verification records, and operation logs in an e‑commerce system, complete with SQL definitions and UI screenshots.
This article explains what stored procedures are, outlines their advantages and disadvantages, argues why they are often not the best choice for modern applications, and shares the author’s perspective along with multiple community viewpoints on using stored procedures in database design.
This article explains the fundamentals of role‑based access control, how roles and permissions are structured, the use of user groups to simplify large‑scale authorizations, and presents a comprehensive database schema—including tables for users, roles, permissions, resources, and logs—to support flexible and extensible permission management.
This article explains why using NULL columns in MySQL can lead to extra storage, complex indexing, and query pitfalls, and provides concrete reasons and examples showing how NOT NULL constraints improve data integrity and performance.
This article explains why HBase rowkey design is critical for performance, outlines common interview expectations, and provides visual guidelines to help developers create efficient rowkeys for production workloads, including best‑practice tips on key length, salting, and ordering to avoid hotspotting.
This guide outlines comprehensive MySQL naming conventions, table and column design rules, indexing best practices, SQL coding standards, and operational recommendations to improve performance, maintainability, and security while avoiding common pitfalls such as redundant indexes, unsafe data types, and excessive batch operations.
This article presents a comprehensive set of MySQL high‑performance optimization guidelines, covering naming conventions, table design, data types, index strategies, SQL coding standards, replication, backup, and operational best practices to improve efficiency, reliability, and scalability of database systems.
This guide outlines comprehensive MySQL best practices, covering naming conventions, basic schema design, field type selection, index strategies, foreign‑key usage, SQL coding standards, batch operations, online schema changes, and permission principles to ensure performant and maintainable databases.
This guide outlines comprehensive MySQL best‑practice rules covering object naming, table engine and charset choices, column design, index strategies, SQL coding conventions, and operational safeguards to improve performance, maintainability, and data integrity in production environments.
This article examines the benefits and drawbacks of database foreign key constraints, highlighting issues such as performance overhead, concurrency bottlenecks, scalability limitations, and increased operational complexity, and argues why handling relationships in the application layer is often preferable.
The article analyzes the shortcomings of traditional disaster‑recovery methods, explains why DB2 pureScale GDPC was chosen for a dual‑active database solution, and provides detailed design guidelines covering site selection, arbitration node, network architecture, storage layout, resource sizing, client connectivity, and the solution’s advantages and limitations.
This article analyzes common disagreements in designing an order status field for e‑commerce systems, explores business state modeling, evaluates dictionary representations, recommends using varchar2 with a separate dictionary table, and provides a comprehensive set of status values and their handling guidelines.
This article examines the definitions, advantages, and trade‑offs of logical (surrogate), business (natural), and composite primary keys in relational databases, offering practical guidelines and best‑practice recommendations for selecting the most suitable key strategy.
This article walks through choosing a web framework and database, introduces relational databases, explains design steps such as requirement analysis, table creation, primary key selection, relationship modeling (one‑to‑many, many‑to‑many, one‑to‑one) with SQL examples, and covers normalization forms, integrity rules, and indexing strategies.
The article analyzes the evolution of e‑commerce product modeling, introduces categories, brands, and attribute‑based filtering, distinguishes products from SKUs, and proposes a backend‑centric data model that supports flexible search, display, and integration with other business services.
This article summarizes the design and evolution of a MySQL cloud DBaaS platform, covering MySQL 8.0 features, the need for DBaaS, multi‑generation architecture, service and data availability strategies, monitoring, DTS design, and upcoming roadmap for broader database support and hybrid cloud deployment.
This guide outlines best‑practice naming rules, storage engine choices, data type recommendations, and a collection of performance‑oriented MySQL techniques—including indexing strategies, query optimizations, pagination methods, and security measures—to help developers design efficient and maintainable database schemas.
This article explains how to design and implement a lightweight rule engine using condition‑based rules and a simple database schema, illustrated with a medical prescription recommendation example, and includes Java code that evaluates logical expressions to determine when to display results.
