The article compares PostgreSQL and MySQL, highlighting PostgreSQL's richer data types, extensible ecosystem, advanced replication and monitoring features, while exposing MySQL's limitations in data modeling, sequence support, tooling, and replication, and concludes that the best choice depends on specific workload requirements.
The article compares PostgreSQL and MySQL across data types, native sequences, extensions, monitoring tools, replication mechanisms, licensing, community governance, and MVCC implementation, showing why many Chinese tech giants favor PostgreSQL for complex, high‑consistency workloads while acknowledging MySQL’s strengths in simple web scenarios.
The article analyzes why many Chinese cloud providers and enterprises prefer PostgreSQL to MySQL, detailing PostgreSQL's richer data types, native sequence support, extensible ecosystem, advanced monitoring, robust replication, open licensing, and MVCC implementation, while acknowledging MySQL's remaining advantages in specific scenarios.
This article compares PostgreSQL and SQL Server data access methods—including sequential scans, index scans, bitmap heap scans, index‑only scans, and parallel query execution—highlighting PostgreSQL's lack of clustered indexes and the performance implications of each approach.
Amid China's push for independent, cloud‑native databases, leading firms like Tencent, Alibaba, Huawei and others have built PostgreSQL‑based solutions, and this article analyzes why PostgreSQL’s richer data types, true sequence objects, extensible ecosystem, advanced replication and licensing advantages make it a preferred choice over MySQL.
The article analyzes why many leading Chinese tech firms adopt PostgreSQL despite MySQL’s popularity, detailing PostgreSQL’s richer data types, native sequence support, extensible ecosystem, advanced monitoring tools, robust replication, open‑source licensing, and MVCC implementation, while also acknowledging MySQL’s strengths in simple deployment and read‑heavy workloads.
The article examines why major Chinese cloud and technology providers are building distributed, cloud‑native or HTAP databases on PostgreSQL instead of MySQL, detailing differences in data types, sequences, extensions, monitoring, replication, licensing, and MVCC implementation.
Amid rising demand for open‑source, self‑controlled databases in China, major firms such as Tencent, Alibaba, and Huawei have built PostgreSQL‑based distributed, cloud‑native solutions, citing PostgreSQL’s richer data types, native sequence support, extensible ecosystem, advanced monitoring, robust replication, and true open‑source licensing as decisive advantages over MySQL.
The article compares PostgreSQL and MySQL, detailing PostgreSQL’s richer data types, true sequence support, extensible ecosystem, advanced monitoring and replication features, while also acknowledging MySQL’s simplicity and strong points, to help readers decide which database fits their workload best.
The article examines why major Chinese cloud providers and enterprises are building PostgreSQL‑based distributed, cloud‑native databases instead of MySQL, detailing PostgreSQL's richer data types, native sequence support, extensible ecosystem, advanced replication, licensing advantages, and MVCC implementation, while also noting MySQL's remaining strengths.
The article compares PostgreSQL and MySQL, highlighting PostgreSQL's richer data types, true sequence support, powerful extensions, built‑in monitoring, advanced replication, open‑source licensing, and MVCC implementation, while acknowledging MySQL's strengths in quick deployment and read‑heavy workloads.
This article compiles a detailed comparison of PostgreSQL and MySQL, highlighting PostgreSQL's lack of text‑size limits, better NULL handling, native array and JSON support, built‑in optimistic locking, superior GIS types, MVCC, flexible indexing, robust replication, and overall stability, while also noting the few areas where MySQL still holds an edge.
The article examines why leading Chinese tech firms are increasingly adopting PostgreSQL instead of MySQL, detailing PostgreSQL‑based products, comparing data‑type support, sequence handling, extensions, monitoring tools, replication mechanisms, licensing, community openness, and MVCC implementation, while also outlining MySQL's limitations.
The article compares PostgreSQL and MySQL, highlighting PostgreSQL's richer data types, native sequence support, powerful extensions, superior monitoring and replication features, and open‑source licensing, while also noting MySQL's simplicity and ecosystem strengths, to explain why many Chinese enterprises choose PostgreSQL for their core databases.
The article compares PostgreSQL and MySQL across data types, sequence handling, extensions, monitoring tools, replication, licensing, and MVCC implementation, showing why many Chinese tech giants prefer PostgreSQL for complex, high‑availability workloads while acknowledging MySQL’s strengths in simple web scenarios.
This article examines why major Chinese technology companies are building distributed, cloud‑native and HTAP databases on PostgreSQL instead of MySQL, detailing PostgreSQL's richer data types, true sequence support, extensive extensions, superior monitoring tools, and robust replication mechanisms.
This comprehensive guide compares MySQL, PostgreSQL, and MongoDB across core features, transaction models, indexing, scalability, and real‑world use cases, offering a step‑by‑step selection method, detailed pros and cons, and a practical decision flowchart to help engineers pick the right database for their projects.
While MySQL remains a reliable, widely-used relational database for simple applications, PostgreSQL’s extensibility, AI-friendly extensions, and growing developer preference—highlighted by recent Stack Overflow surveys—make it the stronger choice for modern, complex workloads, especially those involving vector search, time‑series, and geospatial data.
This article compares MySQL and PostgreSQL by outlining their histories, architecture differences, benchmark results for SELECT, INSERT, and UPDATE operations, and discusses which scenarios each database best fits, helping readers decide which system to adopt for their projects.
This article compares MySQL and PostgreSQL by outlining their architectures, presenting benchmark results that show PostgreSQL’s superior throughput and latency, and discussing the scenarios where each database shines to help developers decide which one fits their project best.
A recent Stack Overflow survey shows PostgreSQL surpassing MySQL in popularity, and the article explains the technical advantages, real‑world performance tests, and evolving use cases that make PostgreSQL the preferred choice for many developers while still acknowledging MySQL’s enduring role for beginners.
This article compares PostgreSQL and MySQL by examining their index structures, query execution costs, data‑type impacts, undo‑log mechanisms, and process models, highlighting where each system excels or falls short in real‑world workloads.
This article compares MySQL and Elasticsearch across data models, query languages, indexing, distributed architecture, performance, scalability, and typical use cases, helping readers decide which system best fits their application requirements in modern software development.
This guide walks you through downloading and installing the DM (达梦) database, creating databases, using the client, mastering basic and advanced SQL syntax, comparing it with MySQL, Oracle, and SQL Server, and highlights its performance, security, and compatibility features.
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.
This article presents a comprehensive benchmark comparing memcached and ScyllaDB across memory, disk, and read‑only workloads, analyzes architectural trade‑offs, and offers practical guidance on when to prefer a simple in‑memory cache versus a persistent wide‑column database.
This article compares MySQL and PostgreSQL, outlining their histories, architectural differences, benchmark results for SELECT, INSERT, UPDATE operations, and discusses suitable scenarios, advantages, disadvantages, and guidance on selecting the appropriate database for various application needs.
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.
An in‑depth comparison of PostgreSQL and MySQL covers their histories, ACID compliance, performance, scalability, advanced features, security, backup strategies, installation on Linux, and provides practical SQL code examples to help full‑stack developers choose the right open‑source relational database for their projects.
This article compares Doris and ClickHouse across architecture, table creation, ecosystem integration, management tools, query performance, and join capabilities, offering practical guidance on how to choose the right database based on your specific data processing and operational requirements.
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 compares PostgreSQL and MySQL across history, ACID compliance, performance, scalability, advanced features, tooling, security, backup strategies, and Linux installation steps, helping full‑stack developers choose the most suitable open‑source relational database for their projects.
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.
An in‑depth comparison of MySQL and PostgreSQL covers their histories, architectural differences, benchmark results showing PostgreSQL’s superior SELECT, INSERT, and UPDATE throughput, and guidance on selecting the appropriate database based on application complexity, scale, and performance requirements.
This article compares MySQL and PostgreSQL, covering their histories, architecture differences, benchmark results, suitable application scenarios, and a concise summary of PostgreSQL's advantages and disadvantages relative to MySQL.
This article surveys emerging database platforms such as PlanetScale, YugaByteDB, Dolt, CockroachDB, Cloudflare D1, Xata, SurrealDB, and FaunaDB, highlighting their architectures, features, pricing, and trade‑offs for developers seeking modern, distributed, or serverless solutions.
This article compares MySQL and MongoDB, outlining their core concepts, shared features such as open‑source licensing and indexing, and key differences in data model, scalability, performance, flexibility, and security, while summarizing pros and cons and recommending suitable application scenarios for each database.
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.
This article presents a systematic performance comparison between Doris and ClickHouse, covering data ingestion speed, SQL syntax differences, hardware impact, and detailed query benchmarks across multiple scenarios, ultimately revealing that each system excels in different use cases.
A comprehensive benchmark shows RedisJSON (RediSearch) dramatically outperforms MongoDB and ElasticSearch in isolated writes, isolated reads, mixed workloads, and latency, delivering up to 200‑plus times faster writes, over 500‑times faster reads, and significantly lower latency across all operation types.
This article examines why PostgreSQL appears to outrank MySQL in recent popularity surveys, explains the DB‑Engines ranking methodology, compares architectural choices such as MVCC, multi‑process vs multi‑thread models, transaction rollback behavior, licensing, and real‑world performance benchmarks like TPC‑C, ultimately revealing that MySQL still dominates many high‑throughput OLTP scenarios.
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 MySQL and Elasticsearch across data models, query languages, indexing, distributed architecture, performance, scalability, and typical use cases, highlighting their distinct strengths and trade‑offs to help developers decide which system—or combination—best fits specific application requirements.
This article provides a comprehensive comparison between PostgreSQL and MongoDB across dimensions such as license, data model, JSON support, performance, reliability, scalability, usability, operability, and ecosystem, helping readers decide which database better fits their application requirements in 2023.
This article compares SQL and NoSQL databases, outlining their advantages, limitations, and ideal use‑cases, and provides guidance on selecting the appropriate technology based on consistency, scalability, and data model requirements.
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.
A detailed 2023 comparison of PostgreSQL and MySQL examines licensing, performance, features, extensibility, usability, connection models, ecosystem, and operability, helping developers decide which open‑source relational database best fits their workloads and long‑term strategy.
This article compares PostgreSQL and MySQL across licensing, performance, features, scalability, security, query optimization, replication, JSON support, CTEs, window functions, and ecosystem, using data from the 2023 Stack Overflow survey and practical experience to help developers choose the right open‑source relational database.
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 2023 comparison examines MySQL and PostgreSQL across history, features, performance, scalability, cost, and migration trends, helping developers decide which relational database best fits their specific application requirements.
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.
A former Oracle MySQL optimizer lead publicly denounces MySQL as a poorly designed database, praises PostgreSQL's strengths, critiques MariaDB, and highlights real‑world migration experiences, offering a balanced view of the ongoing open‑source relational database debate.
Benchmark tests reveal that RedisJSON, powered by RediSearch, dramatically outperforms MongoDB and ElasticSearch across isolated reads and writes, mixed workloads, and latency metrics, delivering up to 500‑fold speed gains, lower latency, and higher throughput, making it a compelling choice for modern data‑intensive applications.
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.
A former Oracle MySQL lead engineer explains why, after five years of work, he finds PostgreSQL a superior open‑source RDBMS, criticizing MySQL’s design flaws, comparing MariaDB, and highlighting real‑world migration experiences and industry perspectives.
A former Oracle MySQL lead engineer denounces MySQL as a poor open‑source database, praises PostgreSQL, critiques MariaDB, and discusses the historical evolution and corporate politics behind these relational database systems.
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 provides a side‑by‑side technical comparison of HBase, Kudu, and ClickHouse, covering their installation dependencies, architectural designs, read/write workflows, query capabilities, real‑world use cases at Didi, NetEase, and Ctrip, and practical operational tips.
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.
This article provides a comprehensive technical comparison of HBase, Kudu, and ClickHouse—covering installation dependencies, architecture, basic read/write and query operations, real‑world use cases at Didi, a Kudu‑based real‑time data warehouse, and ClickHouse log‑analysis practices—highlighting each system’s strengths and trade‑offs for big‑data workloads.
This article provides a detailed comparison of MySQL and PostgreSQL, covering licensing, ACID compliance, SQL standard support, replication models, concurrency control, performance characteristics, high‑availability solutions, external data integration, storage engines, and overall strengths and weaknesses to help readers choose the most suitable open‑source database for their scenarios.
This article compares MySQL and Oracle databases, covering their fundamental nature, security mechanisms, permission models, schema migration considerations, storage concepts, syntax variations, and practical differences such as primary keys, quoting rules, pagination, and data type handling.
In the eighth episode of the MySQL冲冲冲 live series, experts discuss the rise of Chinese domestic databases such as TiDB, OceanBase, and Jusheng, comparing their architectures, ecosystems, and market prospects while reflecting on the broader implications for MySQL‑based distributed systems.
An in‑depth comparison of PostgreSQL and Microsoft SQL Server examines their concurrency, partitioning, indexing, compression, cross‑platform support, and overall performance and scalability, concluding that PostgreSQL generally outperforms SQL Server across these parameters while offering more cost‑effective and flexible features.
The article compares MySQL and PostgreSQL across open‑source licensing, ACID compliance, SQL standard support, replication methods, concurrency control, performance, high‑availability solutions, external data sources, and storage models, highlighting each system’s strengths and weaknesses to help readers choose the most suitable database.
This article reviews six of the most popular open‑source database solutions, detailing their features, pros and cons, pricing models, mobile support, and typical user demographics to help readers make informed technology‑selection decisions.
This article explains what constitutes data inconsistency in Redis, outlines key and value mismatch scenarios, and introduces the open‑source redis‑full‑check tool with usage instructions for efficiently comparing two Redis instances across various deployment modes.
This article provides an in‑depth technical comparison of Apache Kylin and Apache Doris, covering their system architectures, aggregation and detail data models, storage engines, data import processes, query execution, deduplication, metadata handling, performance, high availability, maintainability, usability, schema‑change capabilities, features, and community ecosystems.
This article provides a high‑level comparison of MySQL and PostgreSQL, covering their histories, architectures, licensing, performance characteristics, platform support, standards compatibility, and typical use‑cases to help developers choose the most suitable open‑source database for their needs.
This article examines Snowflake’s rapid rise as a cloud‑native data warehouse, contrasts its architecture and operational advantages with Oracle’s legacy system, and explains how shifting market dynamics, open‑source alternatives, and cloud adoption are reshaping the database landscape.
This article compares SQLite, MySQL, and PostgreSQL across architecture, features, scalability, use cases, and limitations, helping developers choose the most suitable relational database for their specific application requirements.
This article compares MySQL and PostgreSQL across open‑source licensing, ACID compliance, SQL standard support, replication modes, concurrency control, performance characteristics, high‑availability solutions, external data source integration, and storage models, helping readers decide which database best fits their workloads.
An in‑depth comparison of MySQL 8 and PostgreSQL 10 examines feature parity, storage architecture, indexing, memory usage, replication, update overhead, and garbage collection, highlighting how recent improvements narrow the gap and offering guidance on choosing the right database for specific workloads.
This article evaluates MongoDB and MySQL for storing and querying large‑scale precious‑metal market data, detailing hardware setup, version configurations, schema designs, and extensive performance benchmarks across million‑ to billion‑record datasets, and concludes with analysis of memory architectures, data models, and suitable application scenarios.
This article provides a detailed, side‑by‑side comparison of MySQL and PostgreSQL, covering their histories, licensing, feature sets, performance characteristics, extensions like PostGIS, indexing, clustering, transaction handling, and practical guidance on choosing the right database for specific workloads.
This article compares SQL Server, Oracle, and MySQL, outlining each system’s key advantages such as scalability, platform support, performance, and cost, while also detailing their main drawbacks including limited openness, hardware demands, security complexities, and feature gaps, helping readers choose the most suitable database.
This article introduces MySQL and MongoDB, compares their characteristics, and demonstrates simple CRUD commands for each, helping developers understand when to choose a relational versus a non‑relational database based on business needs.
This article provides a detailed comparison of five popular NoSQL databases—HBase, Redis, MongoDB, Couchbase, and LevelDB—covering their data models, performance characteristics, CAP classification, Node.js client options, advantages, drawbacks, and ideal use‑cases to help developers choose the right storage solution for a new Node project.
This article compares relational SQL statements with MongoDB’s document‑oriented commands, presenting a side‑by‑side mapping of concepts and CRUD operations, illustrated with example documents and images to help developers quickly grasp MongoDB’s approach.
The article compares PostgreSQL and MySQL, highlighting PostgreSQL’s strengths in analytics and Oracle compatibility but criticizing its OLTP performance, while emphasizing MySQL’s superior scalability, feature set, and growing ecosystem, and discusses the broader trend of moving away from Oracle‑centric architectures.
This article examines why PostgreSQL claims to be the most advanced open‑source database by detailing its object‑relational model, extensive native data types, large‑scale size limits, robust ACID compliance, powerful indexing options, flexible virtual table features, built‑in functions, language extensions, and how these capabilities compare to MySQL, MariaDB and Firebird.
This article compares MongoDB to traditional relational databases, highlighting advantages such as eventual consistency, document storage, built‑in GridFS and sharding, rich third‑party support, and performance, while also discussing drawbacks like lack of transactions, high disk usage, and limited maintenance tools.
The article explains how Redis's rich data structures enable flexible key‑value schema designs for a user login system and a tag system, contrasting them with traditional relational database approaches and demonstrating practical commands and Python code for common operations.
This article compares Redis with MySQL, outlines their similarities and differences, examines Redis alongside Memcached, EhCache, and OSCache, and proposes a simple high‑availability architecture for Redis, highlighting performance, data model, scalability, and operational considerations.
An in‑depth overview compares eight leading NoSQL databases—CouchDB, Redis, MongoDB, Riak, Membase, Neo4j, Cassandra, and HBase—detailing their languages, licensing, protocols, features, replication models, and ideal application scenarios to help architects choose the most suitable solution.
