-
Notifications
You must be signed in to change notification settings - Fork 57
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
How to use in AWS Lambda #138
Comments
probably the parsing of the files takes too much time.... try to run it with DEBUG=domain* to see what takes so much time... |
Thanks for the response. It seems that the eventstore initialization takes most of the time. Could you please explain meaning of individual fields of events table (DynamoDB) in eventstore? I have some idea but I'd like to be sure. Thanks |
Perhaps @developmentalmadness can help? |
Haven't looked at this for 2.5 years now so I don't remember the mechanics. But we used this in Lambda exclusively on the project I was working on at the time. I haven't followed progress, so I don't know if anything has changed to affect it's ability to run in that environment since. As for the slow initialization time you may want to look at the One other reason could be the first time you initialize the module it will create the table in DynamoDB for you. When it does it waits until the table becomes active. This process likely takes some time as well. |
Thanks for the answers |
Hi,
I'd like to use your project in AWS environment using Lambda. I have already tried but it seems that initialization takes too long (approx. 2 seconds). Any idea what part of the code could be ommited in AWS?
Thanks
Pavel
The text was updated successfully, but these errors were encountered: