Historically, enterprises used traditional RDBMs for on-line transaction processing (OLTP) applications. We affectionately call these systems OldSQL, because they are largely legacy code bases, originally written decades ago. New OLTP applications have more extreme performance requirements than the Old OLTP applications of yesteryears. These are caused by web users directly submitting transactions rather than using a professional terminal operator and by mobile devices (and sensors) enabling transaction submission from many more locations. In a considerable number of modern applications (multiplayer games, risk analysis in electronic trading, gambling, social networks, etc.) OldSQL is cracking under the volume of interactions. This talk contrasts two alternatives to OldSQL in this area:
NoSQL, where both SQL and ACID transactions are jettisoned for better performance
NewSQL, where SQL and ACID are retained, and better performance is delivered through innovative architectures
Clipping is a handy way to collect important slides you want to go back to later.