Skip to content
This repository has been archived by the owner on Feb 8, 2023. It is now read-only.

Switch to use a serverless architecture? #16

Open
gregstewart opened this issue Jun 16, 2016 · 3 comments
Open

Switch to use a serverless architecture? #16

gregstewart opened this issue Jun 16, 2016 · 3 comments

Comments

@gregstewart
Copy link

Sorry Chris this might make a lot of your work redundant, but maybe this is an option to reduce the amount of effort required to set up machines. Consider using Amazon's API gateway and lambda's to have a serverless GraphQL instance.

Caught up with Alex. He did a little investigation and found this.

Anyway just food for thought.

@asavin
Copy link
Contributor

asavin commented Jun 16, 2016

What are the limitations when writing for AWS lambda? Just curious what kind of effort would be to migrate existing app into lambda compatible shape.

@gregstewart
Copy link
Author

@asavin and @chris-goodchild maybe have a chat with the F&M team given their experience with Shepherd?

@chris-goodchild
Copy link
Contributor

All good experience :). I'll catch up with the F&M guys about it. The current setup isn't too complex but the simpler the better!

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

No branches or pull requests

3 participants