Peter Boros discusses a MySQL architecture useful for the majority of projects, backup, online schema changes, reliability and scalability issues, and basics of sharding.
Craig Brozefsky presents the tradeoffs involved with moving to a purely SQL relational model, instead of using an ORM, along with some of the tools built to facilitate this.
Attila Narin discusses AWS concepts: Availability Zones, RDS Multi-AZ deployments, SQS and Auto Scaling, Elastic IP, load balancing, DNS, DynamoDB, Amazon S3, etc., and EC2 best practices.
Charles Cai, Ashwani Roy discuss a robust, cost effective, hypothetical solution to address extreme challenges in financial institutions, from decision making support to pricing and risk management.
Yashwanth Nelapati and Marty Weiner share lessons learned growing Pinterest: sharding MySQL, caching, server management, all on Amazon EC2.
Ori Herrnstadt introduces the Akiban database which solves the problem of joins and combines the best of relational and document databases.
Kenneth M. Anderson shares some of the data modeling issues encountered while transitioning from a relational database to NoSQL.
Rich Hickey deconstructs the monolithic database into separate services, transactions, storage, query, combining them with a data model based on atomic facts to provide new capabilities and tradeoffs.
Koa McCullough presents best practices for running Percona Server and MySQL in the cloud, cloud backups using EBS, Xtrabackup and S3, using Percona Toolkit to simplify operations, and XtraDB Cluster.
Craig Kerstiens presents the history of Postgres, the basics of developing with Postgres, notes on its performance, and tips on querying it.
Eric Brewer takes a look at NoSQL’s history and considers what should be done so the current NoSQL solutions to evolve in order to address the full range of the application needs.
Zardosht Kasheff suggest using 3 rules for indexing SQL databases: Retrieve less data, Avoid point queries, and Avoid sorting.