News for hackers. Stuff that matters.
Re:Postgres 9.2 will feature linear read scalability up to 6... by justinsb on Wednesday April 04, 2012 @07:28PM (#3800447)
I see you work at Google. How about advancing the conversation by telling us how Google stores its sessions?
Re:Postgres 9.2 will feature linear read scalability up to 6... by haberman on Wednesday April 04, 2012 @10:37PM (#3801023)
Let's make a deal. I'll start "advancing the conversation" once you stop misleading people (ie. admit that your initial sweeping claims were incorrect).
Re:Postgres 9.2 will feature linear read scalability up to 6... by justinsb on Thursday April 05, 2012 @01:02AM (#3801374)
Deal. My initial sweeping claims were incorrect.

So: How does Google store its sessions?

Re:Postgres 9.2 will feature linear read scalability up to 6... by haberman on Thursday April 05, 2012 @11:16AM (#3802902)
So 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.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."

Re:Postgres 9.2 will feature linear read scalability up to 6... by justinsb on Thursday April 05, 2012 @12:02PM (#3803160)
Good deal! Agree that traditional sessions are best avoided, but good to know that megastore is suitable for session data.