search

karelz / GitHubIssues

Tools for tracking GitHub issues
MIT License
14 stars 2 forks source link

Explore DbIssues Implementation #151

Open stephenmichaelf opened 7 years ago

stephenmichaelf commented 7 years ago

Which database is best?

karelz commented 7 years ago

I would personally avoid using any DBs which have to be installed. It's just pain. IMO CosmosDB / AzureTables are best choices ... requires cost & usability for out use cases analysis to make the decision.

stephenmichaelf commented 7 years ago

I have created a Persistence page to track this discussion and organize our thoughts. I added your note there.

karelz commented 7 years ago

I think we can keep the discussion in this issue. If we see GH issue doesn't scale / is unreadable, then we can move to wiki page. Thoughts? ... it is easier to keep things in 1 place IMO and now that we moved from work item lists to issues, that's where we should mostly be to discuss details per component ...

We can keep most important info in the top post of this issue, so that it is easier to see latest status / thinking ... that's what we usually do in CoreFX. Works quite well IMO. Advantage of issues: You can get notifications. You can't get them for wiki edits AFAIK :(