Internet Software Architecture at its most basic consists of four goals: Stability, Scalability, Speed, and Security. A good engineer will answer the problems posed to them; a good software architect asks a different question. That’s the fairy tale we tell ourselves. But the real internet is an ogre. It never acts the way we expect and it bashes us in when we least expect it. Eventually security and stability may seem to us so much the Land of Make Believe as we deal with just keeping a site stable. This talk uses an example in each architectural area of the largest social networks on the internet to try to show that even then there can be art in asking a different question. (Even if our answers, painted using PHP, can look like a Jackson Pollock.)
Brian Aker gives the "zinger" lightning talk about the newly announced "Drizzle". This short (under 8 minutes) video captures Aker's highlights of why he started the Drizzle project and how Drizzle is different from MySQL -- both in what has been removed from MySQL and what features Drizzle can accomodate.
Kelly implemented reporting and history-tracking extensions in Postgres. It keeps track of any changes to the system. This has been valuable in letting clients know what happened to their data, where bugs were happening in the system and generally saving our butts. The reporting system takes changes made in a attribute style table structure and arranges them in a standard table type structure for reporting. Kelly will explain why this system was built and how, including limitations of Postgres that had to be accommodated, and an introduction to writin
Learn how MVCC really works, why it's the best thing since sliced bread for concurrent read/write activity, and why it blows the locking approach out of the water. We'll focus on the way MVCC is implemented in Postgres, but the underlying concepts apply to all MVCC-based databases.
For users and developers.
Greg Sabino Mullane is a noted contributor to Postgres.