1 views collected around this technical thread.
This article compares MySQL and Elasticsearch across data models, query languages, indexing, distributed architecture, performance, scalability, and typical use cases, helping developers choose the right system or combine them effectively for various application scenarios.
This article compares Oracle, PostgreSQL, and MySQL across core features, typical use cases, transaction support, storage engines, licensing, provides simplified installation steps, demonstrates basic SQL operations such as creating tables, inserting and querying data, and highlights key differences like auto‑increment handling and string‑matching functions.
A collection of Zhihu users compares SQL Server and MySQL, highlighting SQL Server's superior locking, performance on massive tables, richer backup and restore tools, tighter C# integration, and enterprise adoption, while acknowledging MySQL's free, lightweight nature and its historical limitations.
The article compares MySQL and PostgreSQL, covering their histories, architecture hierarchies, benchmark performance on SELECT/INSERT/UPDATE, suitable use cases, and summarizes PostgreSQL’s advantages and disadvantages relative to MySQL, providing guidance for choosing the appropriate database.
This article provides an overview of MySQL and PostgreSQL, compares their performance in SELECT, INSERT, and UPDATE operations under identical hardware, and discusses suitable scenarios for each database, highlighting the strengths and weaknesses of both systems.
The article analyses the historical, technical, and market reasons why MySQL became the mainstream database in mainland China, contrasts its simplicity and performance with PostgreSQL's advanced transaction and consistency features, and discusses whether PostgreSQL can realistically replace MySQL in enterprise scenarios.
This article introduces MySQL and PostgreSQL, compares their architectures and benchmark results on identical hardware, highlights PostgreSQL's superior read/write performance, and discusses the strengths, weaknesses, and ideal use‑case scenarios for each database system.
This article introduces MySQL and PostgreSQL, compares their architectures and benchmark results, highlights performance differences in SELECT, INSERT, and UPDATE operations, and discusses suitable scenarios and trade‑offs to help developers choose the appropriate database for their applications.
The article introduces MySQL and PostgreSQL, compares their performance through a benchmark on identical hardware, discusses each system’s strengths, weaknesses, and suitable application scenarios, and provides guidance on choosing the appropriate database for different workloads.
This article analyzes the popularity, success metrics, distributed versus centralized architectures, TPC‑C benchmark relevance, and a detailed feature comparison between MySQL and PostgreSQL, concluding which system currently leads in real‑world OLTP deployments.
The article evaluates database success by comparing PostgreSQL and MySQL across popularity, features, licensing, transaction behavior, MVCC, concurrency models, and use cases, showing PostgreSQL leads in complex queries and feature richness while MySQL remains the most widely used OLTP system, especially in China.
This article compares Elasticsearch and ClickHouse across architecture, query capabilities, and performance using Docker‑compose stacks and Python SDK tests, demonstrating that ClickHouse often delivers superior speed, especially in aggregation and regex queries, while highlighting each system’s design trade‑offs.
This article compares Elasticsearch and ClickHouse by outlining their architectures, detailing deployment configurations, presenting benchmark queries and performance results, and concluding that ClickHouse generally outperforms Elasticsearch in many basic search and aggregation scenarios, while also noting each system's strengths and limitations.
This article provides a detailed technical comparison between PostgreSQL and MySQL, covering architecture, stored procedures, transactions, performance, high availability, replication, permission control, SQL support, data types, fault tolerance, table organization, development interfaces, and community maintenance.
The article compares MySQL’s relational tables with MongoDB’s schema‑free documents, detailing equivalent concepts, CRUD syntax, and benchmark results that show MongoDB achieving higher write and query throughput, easier schema evolution, and built‑in sharding, recommending it for new agile projects while suggesting MySQL remain viable for legacy systems.
This article compares Redis, Memcached, and MongoDB, outlining each system's strengths and weaknesses, performance characteristics, storage capabilities, availability, reliability, consistency, data analysis features, and typical application scenarios to help developers choose the appropriate NoSQL solution.
Recent benchmark tests show that RedisJSON, powered by RediSearch, dramatically outperforms MongoDB and ElasticSearch in isolated writes, isolated reads, and mixed workloads, delivering up to 12.7× faster reads, 5.4× faster writes, and significantly lower latency across various operation types.
This article compares MySQL and HBase by examining their architectural designs, storage engines, data access patterns, and ecosystem features, highlighting the strengths and trade‑offs of each system and outlining the scenarios where HBase is a suitable complement to MySQL.
This article presents a detailed technical comparison between Apache Doris and ClickHouse, covering their architecture, deployment, distributed capabilities, transaction support, data import, storage design, query performance, cost, and future development, and provides guidance on selecting the appropriate engine for specific OLAP scenarios.
This article shares an interview experience that compares MongoDB and MySQL, explains the advantages and disadvantages of document‑oriented and relational databases, introduces other NoSQL solutions such as Elasticsearch, and offers guidance on choosing the right storage technology based on workload characteristics.