

What to do when a MySQL/MariaDB database gets too large for a single host?
What are your strategies when a MySQL/MariaDB database server grows to have too much traffic for a single host to handle, i.e. scaling CPU/RAM is not an option anymore? Do you deploy ProxySQL to start splitting the traffic according to some rule to two different hosts? What would the rule be, and how would you split the data? Has anyone migrated to TiDB? In that case, what was the strategy to detect if the SQL your app uses is fully compatible with TiDB?
How can i have my MariaDB database at booth working PCs without exporting and importing the whole database every time i switch the devices?
The database changes from time to time in my project (still early) or i add more test datasets and when i want to switch from my laptop to my desktop i need to "duplicate" the database completely manually.
Is there some way to automatize the export/inport stuff or is it better to have it only on one PC and use the other more for convenience when i code?
I use XAMPP (MariaDB) on booth PCs (Win10).
This is a post in a series about the Apache CouchDB 3.0 release. Check out the other posts in this series. In early 2019, the IBM/Cloudant team proposed a major change to CouchDB: replace the stora…
Writing a SQL database from scratch in Go: 4
Writing a SQL database from scratch in Go: 4. a database/sql driver
Writing a SQL database from scratch in Go: 3
Writing a SQL database from scratch in Go: 3. indexes
When you run queries in ClickHouse , you might notice that the profiler often shows the LZ_decompress_fast function near the top. What is going on? This question had us wondering how to choose the...
Highly Available Prometheus Metrics for Distributed SQL with Thanos on GKE
Learn how to get up and running with Thanos on top of Prometheus to monitor a YugabyteDB cluster, all running on Google Kubernetes Engine (GKE)
We are facing some interesting times at work as we are going to start changing our technology stack in the near future. Most of our Oracle ...
ClickHouse users already know that its biggest advantage is its high-speed processing of analytical queries. But claims like this need to be confirmed with reliable performance testing. That's what we...
Writing a SQL database from scratch in Go: 2. binary expressions and WHERE filters
Writing a SQL database from scratch in Go: 2. binary expressions and WHERE filters
Achieving 10x Better Distributed SQL Performance in YugabyteDB 2.1
Explore some of the performance enhancements in YugabyteDB 2.1, and the results for the YCSB and TPC-C benchmarks
Writing a SQL database from scratch in Go: 1. SELECT, INSERT, CREATE and a REPL
Writing a SQL database from scratch in Go: 1. SELECT, INSERT, CREATE and a REPL
PostgreSQL provides five datetime data types, including timestamp/timestamp with time zone, date, time, interval and time range(tsrange, tstzrange, daterange). This article briefs them, talks about gotchas and recommendations like why not store every datetime in UTC.
ScyllaDB has made a name for itself as a fast drop-in replacement for Apache Cassandra. Now it ups the ante, offering Amazon DynamoDB compatibility and new features, promising superior performance, lower total cost of ownership and no vendor lock-in