Databases are fundamental to every application, and reading or writing data in a quick and reliable way is critical to ensuring happy users. Your shiny new application may have worked well in the beginning, but with more and more people using the app the response times may take a nose dive. Or, what if you push a great new feature, guaranteed to make customers happy, but then it doesn’t scale or it actually degrades the performance of existing functionality? What do you do? How do you diagnose and resolve these issues in a timely and cost efficient manner? Whilst many organizations employ a team of database administrators (DBAs) to manage database performance, it’s often a group separated from development and operational support with their own tools, scripts, and procedures. This creates inefficiency in the root cause analysis process. We want to empower customers by including deep-dive database monitoring as part of end-to-end APM, thereby providing immediate visibility of DB metrics to all groups within IT. This session covers: -Why it makes sense to include the database as part of API -What are some real world problems affecting database performance -What is a good methodology for diagnosing and understanding database performance This deck was originally presented at AppSphere 2015.