TripAdvisor Architecture - 40M Visitors, 200M Dynamic Page Views, 30TB Data • Hacker News Board

Re: TripAdvisor Architecture - 40M Visitors, 200M Dynamic Page Views, 30TB Data

#21

Post by jokull » Mon, Jun 27, 2011, 10:25 PM UTC

I've helped my grandmother manage her business listing on there. It has brought many happy costumers and for at least 4 months a year we have a full booking of all spaces. However, the product is poorly done. It is hard to navigate and there are no tools to share accounts or have multiple listings within one account. I've also encountered numerous technical errors and limitations that make me think the product might not be secure. It feels like the more recent features are sitting on an outdated and overly complex codebase (just a guess).

So if any TripAdvisor employees are listening - thank you for a product that has worked well for us. But if you can improve it I am sure you could bring in more costumers on both ends (managers and travelers).

Re: TripAdvisor Architecture - 40M Visitors, 200M Dynamic Page Views, 30TB Data

#22

Post by websiteguy » Mon, Jun 27, 2011, 10:36 PM UTC

jokull wrote: post #21

I've helped my grandmother manage her business listing on there. It has brought many happy costumers and for at least 4 months a year we have a full booking of all spaces. However, the product is poorly done. It is hard to navigate and there are no tools to share accounts or have multiple listings within one account. I've also encountered numerous technical errors and limitations that make me think the product might…

Hi jokull,

Would like to understand more, is there a way to contact you ?

Andy

Re: TripAdvisor Architecture - 40M Visitors, 200M Dynamic Page Views, 30TB Data

#23

Post by jokull » Mon, Jun 27, 2011, 11:00 PM UTC

websiteguy wrote: post #22

jokull wrote: post #21

I've helped my grandmother manage her business listing on there. It has brought many happy costumers and for at least 4 months a year we have a full booking of all spaces. However, the product is poorly done. It is hard to navigate and there are no tools to share accounts or have multiple listings within one account. I've also encountered numerous technical errors and limitations that make me think the product might…

Hi jokull, Would like to understand more, is there a way to contact you ? Andy

jokull@solberg.is

Re: TripAdvisor Architecture - 40M Visitors, 200M Dynamic Page Views, 30TB Data

#24

Post by hn_decay » Mon, Jun 27, 2011, 11:27 PM UTC

websiteguy wrote: post #20

hn_decay wrote: post #19

Earlier quoted context omitted.

If they are joining across partitions, then perhaps. If they are forced to localize data to make it joinable, whereas doing the "join" at the app level makes it more horizontally scalable, then that might be an impact. However against a single instance if you can join in your app faster than on the database for a trivial join, something is seriously wrong with your implementation. I have never, ever seen such a case…

(disclosure, I am the author of this post) Hi hn_decay, Our use case goes like this: a member database of over a 100M records, and a number of content databases each with tens or hundreds of millions of records (reviews, video, lists, wiki, this, that , the other thing, one content table with over a billion records, where all the content records had a member id. Our primary usage pattern is to grab a set of content r…

I was replying to the context of the post, and specifically spoke to horizontal scalability so I am confused that you felt it appropriate to "correct" that.

Having said that, hundreds of millions of records equals a small dataset. I still don't understand when that's held as some sort of edge case when it's easily accommodated on commodity low-end hardware.