News for hackers. Stuff that matters.
Re:Heroku Postgres by sgrove on Tuesday August 30, 2011 @01:42PM (#2942438)
This is really exciting - the team behind this really cares about developers and their experience. They see a way things could be better, and regardless of technical difficulty, say, "why not?" Forking a db? Brilliant. Offload expensive task to passive followers? Obvious (in hindsight). Instant, brain-dead db provisioning? Of course.

Personally, the only terrifying thing about this is that when Heroku releases something, it's been in the works for a good long while, and they usually have a stream of incredible releases waiting right behind it. The mind boggles at what they're going to be doing next.

But we'll be first in line for it :)

Re:Heroku Postgres by jinushaun on Tuesday August 30, 2011 @02:49PM (#2942704)
When I read "forking" and "following" on there, it was a revelations: of course, that's so obvious! Those terms are much friendlier than "replication" or "master-slave". It describes the desired result, instead of the underlying technology.
Re:Heroku Postgres by pvh on Tuesday August 30, 2011 @02:53PM (#2942719)
If you had any idea how long it took to get that language right...
Re:Heroku Postgres by sgrove on Tuesday August 30, 2011 @03:40PM (#2942923)
I'd be curious to hear the alternatives, and the overall process used to arrive at the current language.
Re:Heroku Postgres by pvh on Tuesday August 30, 2011 @05:55PM (#2943445)
Hmm, this would make a good blog post. I'll draft something up.
Re:Heroku Postgres by DavidChouinard on Tuesday August 30, 2011 @08:17PM (#2943742)
Please do. There seems to be valuable lessons learnt there.
Re:Heroku Postgres by samstokes on Tuesday August 30, 2011 @05:01PM (#2943231)
I seem to remember the term "manumission" being floated around during the beta process... :)
Re:Heroku Postgres by joshuacc on Tuesday August 30, 2011 @05:08PM (#2943254)
Seconded.