MySQL: Problems, Solutions, and Consequences
About two weeks ago, I went with Borya (mathete), Sasha (md5), and Ilya (Troy) to a meetup with MySQL Server developer Dmitry Lenev.
The meetup took place at the Oracle office, whose austere interiors were apparently dictated by the business center itself. I’d prefer Yandex’s interiors, where everything is bright, unusual, and fun, but that’s beside the point…
Dmitry’s talk covers a number of architectural and organizational problems that arose during the development of MySQL Server. It will look at how they were solved, as well as how the choice of one solution or another affected the server’s subsequent development. In particular, it will cover how transactions were added to MySQL, how the product’s development cycle changed, and how the diagnostics subsystem evolved.
http://vk.com/codefreeze?w=wall-37777824_62
I really enjoyed the talk itself. Dmitry spoke about genuinely interesting things, and he was a pleasure to listen to. You can download the talk at this link: http://adw0rd.com/media/uploads/MySQL-CodeFreeze-SPB.pdf
I have nothing to add myself, so I’ll just attach some photos:
And at the end, as always, Borya’s questions: “Why not Erlang?” :-)
Thanks to CodeFreeze for organizing this event!
UPDATE: I just found the videos:
Comments are closed. Read the original discussion in Russian →