search

stemount / cloutbot

A useful Discord bot that lets you validate people who help, contribute and thank with a star.
5 stars 2 forks source link

Pick a database solution that will work across local/stg/production environments #12

Open stemount opened 3 years ago

stemount commented 3 years ago

To keep all the solutions in check, we need to decide what ORM is used so we can support sqlite3, postgres, mysql etc.

stemount commented 3 years ago

... there is also an idea where we could connect cloutbot to a GitHub repository and use it as a flat file DB, there may not even be a need for a relational database at all.

(This could be an epic ORM hack where a custom flat file driver is made for github)

JackBocresion commented 3 years ago

Redis might also be a nice idea as we only need ID => Reputation

ujjwal-kr commented 3 years ago

... there is also an idea where we could connect cloutbot to a GitHub repository and use it as a flat file DB, there may not even be a need for a relational database at all.

@stemount, I'm using the github file db with manual AXIOS requests from nodejs, as a heroku backend. I don't have any complaints about the performance 👍🏻

stemount commented 3 years ago

... there is also an idea where we could connect cloutbot to a GitHub repository and use it as a flat file DB, there may not even be a need for a relational database at all.

@stemount, I'm using the github file db with manual AXIOS requests from nodejs, as a heroku backend. I don't have any complaints about the performance 👍🏻

Hi @ujjwal-kr How did you find our community? :-)

Yes, I think a flat file database would be great, I am wondering how it would scale though to commit every single reputation change e.g. is a 1,000,000 commit Git repo (of really minor changes to a flat file DB) vs committing more changes in a diff every 5-10mins would be?