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.

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

dashboard: Design backend #10

Open
sprt opened this issue Oct 9, 2024 · 1 comment
Open

dashboard: Design backend #10

sprt opened this issue Oct 9, 2024 · 1 comment

Comments

@sprt
Copy link
Collaborator

sprt commented Oct 9, 2024

Goals:

  • Stateless at first
  • Minimal cost
  • Ease of deployment
    • Can we automatically deploy to prod every time a PR is merged to main?
    • Can we easily deploy a local dev environment?
  • Ease of maintenance
  • Ideally: Be able to authenticate each GH user individually so that users don't share a common rate limit. Pretty important so that malicious actors can't DoS us.

Things to look out for:

  • What Azure service to host it on? App Service, Azure Functions, Container Instances
    • Argue pros and cons (e.g. I know Az Functions can have high latency)
@sprt sprt converted this from a draft issue Oct 9, 2024
@chris-krenz
Copy link

Per Aurelien's comments, using something like Functions might cause a latency problem with cold starts:

https://azure.microsoft.com/en-us/blog/understanding-serverless-cold-start/

In creating this proposal, I'll be sure to include a few different options with their pros and cons (and then a recommendation).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

No branches or pull requests

2 participants