erlang - NoSql - which is best for my needs - i am having mental breakdown -


I am creating a reddit clone in Erlang. I am considering using some erlang web frameworks but This is not a problem.

I'm having trouble choosing a database

how it works;

I have several dedicated reddits examples, science, funny, corporate, games you can consider them sub reddits each sub reddit categories.

A user can post the following information:

Title, Category Tag, Description, Category, Future Date ,

Add more pictures, link video

With Reddit, users will be able to vote on stories and comments. Comments will also have a vote system.

How the problem;

I do not know what kind of database to use, there are scalability problems with the MyScl on the site (trust me if it will not suggest

now I Which is required,

1) A user will go to Sporting Saabreadet,

P> They will want to see all the stories with the future date , For example in the NFL category, or in the Soccer World Cup category they date of the future Or , which show upcoming games or events.

But when people can write bullshit, then I need to sort them by the date of the future, but then filter by posting the results with more than 5 votes, then I will get the next upcoming event.

So if there is a game on the weekend and the next game 3 weeks then the closest game needs to come first.

2) So the above problem is using a database

1) Find all posts in subredit: game . 2) Find many posts in the NFL category . 3) Find all posts with Future date Sort these posts by Most votes and display the nearest date stories for today < / P>

I think couchbad looks like a good candidate, but I'm not sure

But what about Casandra, Hubbus, Riek, NEO 4j?

I am trying to figure out what I'm going crazy.

I have some things that scale and handle users on a large scale.

Please help, thank you

Cassandra should work well for you; "Users who are shown in different ways," they are very similar to the ones who are giggling (and they are completely moving forward for the cassandra).

The name of the game in Cassandra is denormalization. Therefore, for each category or episode you will have a row in the post if you are inquiring about relatively small numbers at a time, then you can probably dislike post information (with vote count) and only remove multigayet . For larger batches, you should duplicate each post column so that you do not have to pay extra extra.

If you temporarily use some columns to order as a timuiuid, then "give me everything in class X that after today's date" is trivial, and then you vote Sort by customer side count (why not sort server side? Because this scale is not.)


Comments

Popular posts from this blog

c# - How to capture HTTP packet with SharpPcap -

php - Multiple Select with Explode: only returns the word "Array" -

php - jQuery AJAX Post not working -