Twitter | Search | |
@rem Jun 1
If I'm using a database in AWS lambda, is there any other option beyond RDS? I'm trying google firebase, but it's adding a full 1 second to the exec time (checked with server timings)
Reply Retweet Like
xnoɹǝʃ uɐıɹq 🐻 Jun 1
Replying to @rem
Dynamo is the main option still. It's the best performance vs anything else by a wide margin. Also using S3 w flat json files is pretty good! I wrote a Dynamo wrapper to make it nicer:
Reply Retweet Like
@rem Jun 1
Replying to @brianleroux
Am I right in thinking that 1 second is too long for db activity in a lambda?
Reply Retweet Like
xnoɹǝʃ uɐıɹq 🐻
It's definitely too long but normal for anything other than ddb unfortunately. (Dynamo stays within 9ms for any query.)
Reply Retweet Like More
Joe McCann Jun 1
Replying to @brianleroux @rem
*any* query? I've had > 9ms latency for sure from dynamodb queries, not scans. Teach me the ways!
Reply Retweet Like
xnoɹǝʃ uɐıɹq 🐻 Jun 1
Replying to @joemccann @rem
Should qualify: they guarantee "single digit millisecond latency" per page of data where one page eq 1 mb. But ya that's what we see w arc/begin.
Reply Retweet Like
Joe McCann Jun 1
Replying to @brianleroux @rem
Gotcha thanks for clarification
Reply Retweet Like