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

Deployment options #24

Open
petr-tik opened this issue Apr 25, 2018 · 2 comments
Open

Deployment options #24

petr-tik opened this issue Apr 25, 2018 · 2 comments

Comments

@petr-tik
Copy link
Member

petr-tik commented Apr 25, 2018

Thinking about the use cases of the API and how it's going to influence the deployment options.

API use cases:

  1. ffig explorer web application
  2. curl/CLI like godbolt's compiler explorer API

API requirements/constrains:

Dependencies - llvm, libclang, python (we have golang and luajit as dependencies - are they used by ffig to generate bingings or are they only for testing?)
If I understand correctly, our API is stateless and doesn't need storage?

Deployment options:

For a stateless API with <10 endpoints and a mostly idle time, it feels wasteful to reserve a DO instance.

AWS Lambda

Pros:
  • Cheaper - not paying for idle time
  • indefinite free tier
Cons:
  • Some runtimes aren't available (luajit)
  • Overwhelming

Digital Ocean - reserved instance

Pros
  • Proficiency - have set one up before
  • Full control over all necessary runtimes, deps
Cons
  • Costs more

@jbcoe thoughts?

@jbcoe
Copy link
Collaborator

jbcoe commented Apr 25, 2018

We have no money as it stands. Will need to ponder.

@petr-tik
Copy link
Member Author

AWS Lambda has a free tier, which is offered indefinitely (as of now anyway). Will add it to pros for AWS lambda

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

No branches or pull requests

2 participants