7 ms·
This article contains a number of fallacies. Storing sessions on disk? Over NFS? In the database? Please - no-one does that. And random MySQL bashing? What's th
by mpk 14y ago
This article contains a number of fallacies. Storing sessions on disk? Over NFS? In the database? Please - no-one does that. And random MySQL bashing? What's that based on? MySQL is used by many high-volume shops to handle huge amounts of data. (See - I don't have to quote examples either!) And magic Oracle scales to infinity? For the kinds of database setups you need with high-performance web apps you can throw the same amount of money at percona.com and get there as well.
[Edit - didn't notice this was a 2004 article]
- Xylakant 14y agoDisk-based session storage was the default for years and still is. I know of some high-volume sites that used NFS as the sharing mechanism at least up to 2008 and I assume they still do. It kinda works if you do mostly reads. Storing the session in the database was the prime example when session_set_save_handler() was first introduced. The symfony framework still ships with a pdo session handler, so I'd assume people still use it [1] The memcache session handler had major problems with session locking at least as of 2008, I don't know if it's been fixed by now. [1] https://github.com/symfony/symfony/blob/8ebe624b82dc9f91231ec2a4361468579495cdd8/src/Symfony/Component/HttpFoundation/Session/Storage/Handler/PdoSessionHandler.php https://github.com/symfony/symfony/blob/8ebe624b82dc9f91231e...
- iand 14y agoRemember this is from 2004, people were doing those things at that time.