-
Notifications
You must be signed in to change notification settings - Fork 0
Open
Description
Thinking about the use cases of the API and how it's going to influence the deployment options.
API use cases:
- ffig explorer web application
- 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?
Metadata
Metadata
Assignees
Labels
No labels