Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

As a developer we have to choose question how we recommend #5

Closed
Jevli opened this issue Nov 10, 2017 · 4 comments
Closed

As a developer we have to choose question how we recommend #5

Jevli opened this issue Nov 10, 2017 · 4 comments

Comments

@Jevli
Copy link
Owner

Jevli commented Nov 10, 2017

We need choose what is question/algorithm and data what we use for recommendation
@Jevli
Copy link
Owner Author

Jevli commented Nov 16, 2017

I would say that more closer events are more important.

Adding user to be able to rate event would be also good. (We could keep data base of users ratings)

Maybe we should have
user, events and ratings tables? (so sql database)
or user (with ratings) and events (document database)

@mmercurious
Copy link
Collaborator

Would it be easier to understand if users, events and ratings had their own tables? I'm not against having user with ratings though.

@Jevli
Copy link
Owner Author

Jevli commented Nov 17, 2017

It woudn't be bad plan, probably wiser. though then we have to use relation database. (I will choose one for us :) )

@Jevli
Copy link
Owner Author

Jevli commented Nov 17, 2017

Cassandra (mysql) chosen for database.

@Jevli Jevli closed this as completed Nov 30, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@Jevli @mmercurious