3 ms·
I see you work at Google. How about advancing the conversation by telling us how Google stores its sessions?
by justinsb 15y ago
I see you work at Google. How about advancing the conversation by telling us how Google stores its sessions?
- haberman 15y agoLet's make a deal. I'll start "advancing the conversation" once you stop misleading people (ie. admit that your initial sweeping claims were incorrect).
- justinsb 15y agoDeal. My initial sweeping claims were incorrect. So: How does Google store its sessions?
- haberman 15y agoSo I'm not an expert in Google's front-ends and I'm not sure that Google stores "sessions" in the way you'd generally think of them in web apps. But usually when we have requirements like what you'd need for sessions (highly available, low-latency, highly scalable) we use Megastore: http://www.cidrdb.org/cidr2011/Papers/CIDR11_Paper32.pdf http://www.cidrdb.org/cidr2011/Papers/CIDR11_Paper32.pdf http://www.readwriteweb.com/cloud/2011/02/megastore-googles-answer-to-no.php http://www.readwriteweb.com/cloud/2011/02/megastore-googles-... Megastore is a layer on top of Bigtable that adds indexing, synchronous replication across data centers, and ACID semantics within small partitions called "entity groups."
- justinsb 15y agoGood deal! Agree that traditional sessions are best avoided, but good to know that megastore is suitable for session data.