Slideshare uses cookies to improve functionality and performance, and to provide you with relevant advertising. If you continue browsing the site, you agree to the use of cookies on this website. See our User Agreement and Privacy Policy.

Slideshare uses cookies to improve functionality and performance, and to provide you with relevant advertising. If you continue browsing the site, you agree to the use of cookies on this website. See our Privacy Policy and User Agreement for details.

Our application got popular and now it breaks

1.
Our application got popular,
and now it breaks
Dan Wilson

2.
Who is Dan
Wilson

Runs ChallengeWave.com,
Datacurl LLC and NCDevCon

Specializes in project
rescue, high performance
applications and development
team evaluation

Owner of Model-Glue

Dad of 2, Husband to 1

Loves all things technical
and a good debate

15.
● Session Scope use is the largest culprit
● Sometimes you have to deoptimize a few
operations in order to provide a scalable
solution (like stop caching a state query in application)
● If you want to use a shared scope and want to
keep an eye on scalability later, use a lookup
factory.
Over-reliance on Shared Scopes

28.
<cfquery name="PeopleToFire" datasource="#db#">
SELECT emp.employee_number, emp.name
FROM emp
INNER JOIN
(
SELECT department,
AVG(salary) AS dept_avg
FROM employees
GROUP BY department
) AS deptAvg
ON emp.department = deptAvg.department
WHERE emp.salary > deptAvg.dept_avg
</cfquery>
This is not like a query in a loop