-
-
Notifications
You must be signed in to change notification settings - Fork 93
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
Scaling related questions #143
Comments
How'd you split the resolvers to different lambdas? I guess it could be possible but not sure whether it's possible with current implementation of this package as the connection management is handled directly in lambda handler and you need to use correct connection ids, to communicate with subscribers. So the problem would be how to recreate proper context in resolvers. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
I have been enjoying using this library and I have a few questions about the scaling.
If I am going to add more lambda functions and split resolvers into different lambda functions, what can I do?
Is it feasible with the package?
The text was updated successfully, but these errors were encountered: