News for hackers. Stuff that matters.
Re:Rethinking caching in web apps by lifeisstillgood on Monday October 01, 2012 @08:04PM (#4600007)
Ok, I'll bite

is this sharding or is the whole dbase in each instance if the latter how do you deal with two instances selling the same room on same day ?

It seems nice but do they recieve updates from each other or is it fed in from the back end. Either way the nice simplicty gets all confused haning updates

Re:Rethinking caching in web apps by jdpage on Monday October 01, 2012 @08:26PM (#4600084)
Does RoomKey actually sell individual rooms, or just hotel bookings? I've never used it, but looking at the site, it seems like it's just selling "a room at a hotel", rather than "a particular room at a hotel".
Re:Rethinking caching in web apps by cvillecsteele on Tuesday October 02, 2012 @09:38AM (#4601854)
Hi, I'm the author. We are a new online travel agency (OTA), like pricline, et. al., but different in that we don't take the booking - we send you off to the actual hotel website to book.
Re:Rethinking caching in web apps by lifeisstillgood on Tuesday October 02, 2012 @07:07PM (#4604878)
So the hotels have finally worked out lastminute.co is bad for them and started offering affiliate fees? Interesting - that could open up a lot of options - is that how it's working for you?
Re:Rethinking caching in web apps by cvillecsteele on Thursday October 04, 2012 @09:25AM (#4612162)
I'm not complaining. :)
Re:Rethinking caching in web apps by cvillecsteele on Tuesday October 02, 2012 @09:39AM (#4601857)
Since we send the visitor off to the owning hotel chain's website to book, we don't have to manage the complexity of update such as you're describing.