otto

It has been long in the coming (Oracle bought Sun and MySQL over 15 years ago), but seems WordPress is finally at the point where MariaDB popularity surpassed MySQL as shown by stats at https://wordpress.org/about/stats/.

The share of MySQL 8.4 users is oddly low, just 0.1 %. One would think it would still be at least 1% or something..

What are your preferred strategies when a MySQL/MariaDB database server grows to have too much traffic for a single host to handle, i.e. scaling CPU/RAM or using regular replication is not an option anymore? Do you deploy ProxySQL to start splitting the traffic according to some rule to two different hosts?

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?

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?

Besides having the latest version available, what do Ubuntu users who run MariaDB wish to see in future versions of MariaDB, or how it is integrated and packaged in Ubuntu?

I am the maintainer in Ubuntu - looking for feedback and ideas.

The XZ Utils backdoor, discovered last week, and the Heartbleed security vulnerability ten years ago, share the same ultimate root cause. Both of them, and in fact all critical infrastructure open source projects, should be fixed with the same solution: ensure baseline funding for proper open source maintenance.

The XZ Utils backdoor, discovered last week, and the Heartbleed security vulnerability ten years ago, share the same ultimate root cause. Both of them, and in fact all critical infrastructure open source projects, should be fixed with the same solution: ensure baseline funding for proper open source maintenance.

The XZ Utils backdoor, discovered last week, and the Heartbleed security vulnerability ten years ago, share the same ultimate root cause. Both of them, and in fact all critical infrastructure open source projects, should be fixed with the same solution: ensure baseline funding for proper open source maintenance.

Having smart people with a lot of knowledge results in progress only if information flows well in the veins of the organization

In this post, I share 8 principles I believe in:

1. Less is more
2. Start with the solution or the ask
3. Show the facts, with examples
4. Always quantify
5. Include links and references
6. Explain why it matters
7. Ask feedback from one person
8. Sleep on it

As engineers and developers, we often focus heavily on technical skills while neglecting the importance of clear, compelling writing. But the reality is, our ability to communicate effectively can have a major impact on our careers.

There is more to it than just knowing Ctrl+T - see tips to boost your productivity

And to be productive also: git citool, gitk, fzf and Liquid Prompt explained with screenshots