In this paper we present 10 rules that any customer would be wise to keep in mind when considering a database management system (DBMS) application that requires scalable performance, and that reads or writes a small number of objects in each transaction. Such simple operation (SO) applications include on-line transaction processing (OLTP) and also interactive web applications such as social networking. Some of our rules concern the underlying DBMS; the rest are guidelines for architecting scalable DBMS applications. Most existing SO DBMSs satisfy only a few of our rules, so this paper also represents a mandate for future improvement
To submit an update or takedown request for this paper, please submit an Update/Correction/Removal Request.