Gleam Lab · Blog Archive
Blog Page 19
Technical exploration and engineering notes, 655 articles in total.
MySQL Scaling Guide: Triggers, Migration, and Performance Optimization
Explore MySQL database horizontal scaling solutions for capacity, performance, and concurrency bottlenecks.
MySQL Sharding-JDBC: Lightweight Sharding and Read-Write Separation Middleware
A comprehensive guide to Sharding-JDBC, a lightweight Java database middleware solving database sharding, read-write separation and distributed transactions.
MySQL Sharding-JDBC: Physical Tables, Logical Tables and Binding Tables
In distributed databases, sharding is implemented through physical tables, logical tables, data nodes and binding tables.
MySQL ShardingSphere: SQL Parse, Route, Rewrite and Execution Flow
Deep dive into ShardingSphere's sharding flow including SQL parsing, query optimization, SQL routing, SQL rewriting, SQL execution and result merging six major stages wit...
MySQL Read-Write Separation: Master-Slave Architecture Design and Routing
Read-write separation is a common database architecture optimization technique that separates write operations to master and read operations to slaves through master-slav...
MySQL ShardingSphere: SQL Support, Limitations and Optimization Practices
Deep dive into ShardingSphere's SQL support scope, limitations, and optimization practices in sharding scenarios. Learn about supported SQL types, pagination subquery res...
MySQL Sharding-JDBC: Physical, Logical and Binding Tables Explained
In distributed databases, sharding uses physical tables, logical tables, data nodes and binding tables for efficient data storage and queries.
MySQL ShardingSphere Hint Forced Routing: Mechanism and Best Practices
In distributed database scenarios, ShardingSphere provides the Hint mechanism to force routing by explicitly specifying sharding values outside SQL, bypassing the default...
MySQL Distributed Transactions: TCC, Message Queue and Saga Patterns
Distributed transaction patterns mainly include TCC, message queue, and Saga.
Seata Framework: Four Transaction Modes & Core Architecture
Seata is Alibaba's open-source distributed transaction solution providing one-stop transaction management with high performance, low intrusion and multi-language support.
MySQL XA Distributed Transactions: ShardingSphere Integration and Practice
Traditional approaches rely on database vendor XA drivers and application server transaction managers. Modern systems use embedded transaction managers.
CAP Theory & Distributed Transactions: From 2PC/3PC to XA
CAP theory reveals that distributed systems cannot simultaneously satisfy consistency, availability and partition tolerance.
ShardingSphere Data Masking: Transparent Encryption and Compliance
Data masking is a key data security technology that balances data utility and privacy protection by replacing, encrypting or perturbing sensitive information.
ShardingSphere Saga Flexible Transaction Implementation
ShardingSphere's flexible transactions are implemented through the third-party servicecomb-saga component, using SPI mechanism for dynamic injection.
MySQL MyCat Distributed Database Middleware: Architecture and Core Principles
MyCat is an open-source distributed database middleware fully compatible with MySQL protocol.
Sharding-Proxy: Zero-Code-Invasive Database Sharding Solution
Sharding-Proxy is one of the core products in the Apache ShardingSphere ecosystem, using a transparent database proxy architecture.
MyCat Sharding Strategies: E-R, Global Tables and Sharding Rules
MyCat distributed database sharding strategies include E-R table sharding, global table mechanism, shard nodes, node hosts and sharding rules.
MyCat server.xml: Core Configuration File Guide
server.xml is MyCat's core configuration file, storing almost all system configuration information needed by MyCat.
MyCat Installation and Configuration: Setup, Service Management and Schema Files
MyCAT is an open-source database middleware supporting MySQL protocol, commonly used for database sharding and data sharding management.
MySQL Transaction Isolation Levels: From READ UNCOMMITTED to SERIALIZABLE
MySQL transaction isolation levels include READ UNCOMMITTED, READ COMMITTED, REPEATABLE READ and SERIALIZABLE. Each level solves different concurrency problems.