Status/Resolution/Reason: Closed/Withdrawn/Duplicate
Reporter/Name(from Bugbase): Dan Wilson / Dan Wilson (Dan Wilson)
Created: 07/01/2015
Components: Caching
Versions: 11.0
Failure Type: Enhancement Request
Found In Build/Fixed In Build: CF11_Final /
Priority/Frequency: Trivial / Unknown
Locale/System: English / Other
Vote Count: 10
Duplicate ID: CF-3941961
Applications often grow in popularity and usage over time. Many ColdFusion applications are built with many references to session in the code. Using the session is helpful but presents scalability issues because session replication is not perfect and Sticky Session Load Balancing can often result in imbalanced load.
A more preferrable solution would be to configure a connection string to a distributed cache in the Application.cfc (per-application scope) AND/OR in the CF Administrator to allow all session references to point to a distributed cache.
By doing this, an application faced with horizontal scaling issues would be able to decide where to store the session information. This information can be stored in a single distributed cache and reference by many application servers.
Railo 4 already does this and frankly, there are circumstances where it would be more cost effective to move all code to Railo and retest, versus update 2,000 instances of session.whatever in the code.
Here's how it was done in Railo: http://www.getrailo.org/index.cfm/whats-up/railo-40-released/features/application-management/#applicationcfc_settings
So this feature is necessary to keep ColdFusion competitive for applications that are successful and need better horizontal scaling.
----------------------------- Additional Watson Details -----------------------------
Watson Bug ID: 4015193
External Customer Info:
External Company:
External Customer Name: Dan
External Customer Email:
External Test Config:Attachments:
Comments: