2 ms·

I can't see why you can't serialize session to database or memcache or anything else if you want. The amount of code involved is almost zero... Also I don't see

I can't see why you can't serialize session to database or memcache or anything else if you want. The amount of code involved is almost zero... Also I don't see a reason to have a shared storage for session objects in a scalable distributed application you are trying to build. In Java you could, for example, use ehcache with out-of-box replication - simpler than using external C-based application like memcache. And in Java world you have to deal with different applications servers (Weblogic/WebSphere/JBoss etc.) where apache http and nginx installation and configuration is very primitive in comparison. Yes, it involves sharp skills when it comes to huge loads and replication, but that's another story. Your friend is probably a young junior developer, you can't be a serious java developer without a decent server skills - there is no ops team at home to do it for you and you can't really gain a lot of knowledge only doing stuff at work.

mgkimsal 14y ago
Friend in question is certainly not a young junior dev - >10 years of dev experience, 8 in java, and does java training. Trainers may be more focused on language stuff vs admin stuff, so I cut some slack there. But.. the majority of java people I've known have been developers only, who don't do any server admin. Again, not saying java devs who know sys/server admin don't exist, but, the ones I know who do that aren't 'java devs' in the sense of only doing java, but tend to be polyglots with experience from multiple backgrounds. I'm not sure why you'd not have a shared storage for session data in a multi-server system. What else do you suggest? http://ehcache.org/documentation/configuration/configuration http://ehcache.org/documentation/configuration/configuration - that's an insane amount of configuration it looks like compared to something like PHP. It also looks like you're tying yourself to a specific caching solution vs having generalized session data.

mgkimsal 14y ago

Friend in question is certainly not a young junior dev - >10 years of dev experience, 8 in java, and does java training. Trainers may be more focused on language stuff vs admin stuff, so I cut some slack there. But.. the majority of java people I've known have been developers only, who don't do any server admin. Again, not saying java devs who know sys/server admin don't exist, but, the ones I know who do that aren't 'java devs' in the sense of only doing java, but tend to be polyglots with experience from multiple backgrounds. I'm not sure why you'd not have a shared storage for session data in a multi-server system. What else do you suggest? http://ehcache.org/documentation/configuration/configuration http://ehcache.org/documentation/configuration/configuration - that's an insane amount of configuration it looks like compared to something like PHP. It also looks like you're tying yourself to a specific caching solution vs having generalized session data.