Another good day today: I attended the keynotes and found them quite interesting.
I especially liked the way Twitter uses MySQL to build up a NoSQL solution. Jokes aside, I took a few notes on things I must analyze and dig in.
The introduction of the Paypal models seemed very interesting, which brought me to attend the presentation later on. It was well constructed and had some good theoretical work, but I was quite disappointed. I found the presentation incomplete and missing real numbers for the MySQL Cluster NDB setup.
I attended the presentation done by Ronald B. It was good — nothing really advanced, but it was on purpose. He was very informative and explanatory for a junior MySQL DBA, and I enjoyed his presentation for the logical approach and construction.
Ronald also highlighted that it was the content of less then a chapter of one of his books and was done on purpose to give an initial understanding of how to make a good index. Honestly, he was really clear, and I am sure that any DBA in the room now knows how to have Extra: Using Index.
After that, I had my own presentation on Scaling with Master synchronous replication. The audience and open discussion were great. I loved it.
Danil presented in the same room after me. He talked about Slave replication war stories, and he had a good talk as well with a lot of interaction. I found it great that we both presented FACTS and not assumptions or theoretical thing. Both presentations made it clear that we were talking about real events and cases based on experiences gained while working with customer data.
That led me to think once more about how we at Pythian are in a privileged position, given that we have unbelievable combination of practical and cross technology experience. Having done 25 years of work in IT, I can say that this is really unique. No other company can claim to have such variety and combinations like we do.
I can say that it was a good event. It’s probably far from being completed, but it’s at least a good start.
From my point of view, we have learned that:
- Oracle developers must communicate and show more of what they are doing.
- We must be more interactive with the development process, especially with products like MySQL Cluster and MySQL utilities.
- We need to enlarge the base and have other actors given at the end, since almost 80% use the main MySQL strem.
- Conferences MUST have better definition of the tracks by levels, like beginner, intermediate, and expert. This would avoid having Senior people in a presentation for beginners and vice versa.
- Exhibitions need to involve more companies. I am sure it will be like that next year.
- Finally: PLEASE call it as it should. It’s said MY S Q L, not “mysequel”. At least make an effort during the official MySQL conference.
2 Comments. Leave new
If you’re going to be a stickler about how it’s pronounced, why not call it “mee”-SQL? since it’s named after Monty’s daughter?
In other words, it doesn’t really matter if people call it “my-SQL” or “my-sequel” because either way, it’s wrong – the first part isn’t “my” anyway. (and really, it’s silly to complain about it, but whenever people do, I point out that both are wrong anyway).
Sheeri,
the right way to pronounce of MySQL as a name of a company/product is My S Q L.
Rule in MySQL was that we were suppose to say it correctly, then if a customer was saying it wrong, we were not suppose to correct him, just continue using the right way.
Said that I am still feeling my-squel annoying given it is wrong in respect of the Product Name. What is in English is not really relevant, or I should go around and change all the Italian restaurant names in US written in crazy ways.
Have a nice one.