A number of months ago, possibly a year ago, I wrote an internal letter to the MySQL internal discuss list with the title of "The Death of Read Replication". Ever since then I've been getting pinged internally to publish my thoughts on this externally.

Here goes :)

Read replication is going to be in use for many years into the future. There are plenty of reasons to use it, and plenty of setups where it will make sense.

All of the scripting, management daemons, and ease of use scenarios will not solve its problems though, and I am finding that users have either moved away from it, or more often, have reduced their need for it.

A few reasons:
Latency is painful to manage.
Lots of servers means more head count (both disks and in numbers of people to manage it)
In web usage, the rule of thumb is to keep your query number under 7, for this reason you try make more out of …

Faced with the challenge "to figure out a way for memcached servers to replicate data concurrently with the MySQL databases," across the country, Facebook came up with a clever solution of "embedding extra information in to the MySQL replication stream that allows [Facebook] to properly update memcached [servers] in Virginia."

This is very smart! I am curious about how they implemented this. I wonder if by "replication stream" they are just referring to binary logs. The article didn't mention whether they hacked MySQL to do synchronous replication as well, like Google. That would be really neat: synchronous replication that updates memcached.

Synchronous or not, the idea is still uber cool and I would love to see more …

For reference:
http://highscalability.com/skype-plans-postgresql-scale-1-billion-users

Here are some observations by me on the state of database usage in Web 2.0:
All major web 2.0 sites now use object caching (of one type or another)
Sharding and now Proxy style solutions are becoming commodity. They are everywhere.

What does this mean?

Replication is dead except for replicating for "application" needs.

Good News :)

For MySQL it encourages multiple engines. For Postgres I suspect their flexible index design will be useful. The "I replicated over here for a backup, or to run reports..." is still happening a lot. Multi-master replication is one scenario to achieve high availability (DRBD on the low end... you will go broke trying to deploy …

I’ve managed my first week (well 4 days) at my new employer PrimeBase Technologies. Another open source company, a different open source company, my second in succession . A company that actually has it’s parent roots in the commercial sector and this is now branching into Open Source and supporting the community.

While my departure from MySQL was really no surprise to friends within the MySQL community, just some shock of the accelerated timing. Actually it should not have been a shock to my employer either as I’d expressed clearly these intentions in two reviews in the past twelve months. My April Fool’s managed to shock and catch out many to continue this saga.

Our focus has been the …

Here are two basic tips for proper indexing ...Don't mess with datatypes, too often people refer to an attribute defining it as one datatype in a table and as another in different tables, this actually prevents index usage in joins (forget about FKs for this time ;)) See an example here. You could declare a function based index as a workaround, but why don't we all try to make it right?Put

There was just a thread on the Freenode #mysql IRC channel with someone wanting to switch off and delete their binary logs. Why? Because they were short on diskspace.
Mind you, this was a production system, so generally it's rather a bad idea to disable binary logging there, unless you really don't value your data - but in that case you might as well just close down your shop now ;-)
This is not about MySQL reliability, but hardware can and will fail, and all kinds of other things can and will go wrong over time.

While I appreciate the jam this person was in today: choosing between not being online at all, and disabling the binlog for now.... it's so much better to prevent this. I actually hear about database servers running out of disk space quite often so this is a common event!
It's something to keep a close eye on, for instance using Nagios, and have an alert …

A few months ago, I wrote about the issues you will face with installing MySQL on OS X 10.5, Leopard. I am pleased to inform everyone, that this problem has been fixed!

The bug in question, mysql#28854, clearly stated that the problem was with the PrefPane. On Valentine’s Day 2008, Alfredo Kojima (of Workbench fame) fixed the problem, and uploaded a new PrefPane, to ftp://ftp.mysql.com/pub/mysql/download/gui-tools/MySQL.prefPane-leopardfix.zip.

This fixes an incompatibility with the default shipped PrefPane. The new PrefPane also detects if the MySQL data directory (/usr/local/mysql/data) has the incorrect permissions (and if so, one should …

Plenty of people have been excited by the prospect of Amazon EC2 and the ability to scale out your databases as load increases from your original configuration. I noticed Morgan Tocker and Carl Mercier are going to be presenting on this topic at the upcoming MySQL ConferenceHowever almost immediately people are worried about the lack of persistent of data across instance terminations.In a sense

Plenty of people have been excited by the prospect of Amazon EC2 and the ability to scale out your databases as load increases from your original configuration. I noticed Morgan Tocker and Carl Mercier are going to be presenting on … Continue reading →

Reading Mike Zinner's What Does a Workbench SE Subscription Include?, I noticed something other may not fuss about... for $99/seat you get a year of updates, and the basic license does not expire at all.

Workbench has an interesting history... Mike originally wrote DB Designer 4. I first met Mike years ago at a LinuxTag (2003). The program rocked. I introduced Mike to Kaj and said "you two should talk". And thus Mike got hired. He's since been in charge of the MySQL GUI tools, but the successors of DB Designer kept being put off and restarted from scratch: different/changing development priorities and lack of people resources....

I'm still interested in Workbench, although I am concerned that this is like the 3rd iteration of the product, and it now has .Net dependencies. Will it work under Mono? Yes, so we're told; the roadmap says the other platforms …