Viewing profile — munns
munns
HN member- Joined
- Thu, Jun 01, 2017, 1:26 AM UTC
- HN karma
- 695
- Public activity
- 86 items
- HN profile
- View on Hacker News ↗
About munns
No profile information was provided.
Recent public activity
-
comment
Comment #45372354
from the post: Combining Cloudflare Workers, Hyperdrive, and PlanetScale relational databases allows you to build modern globally distributed applications without worrying about da…
- story
-
comment
Comment #45334770
Thanks for that callout, absolutely right. Fixed!
- story
-
comment
Comment #26863280
IN a direct reply to Op: There is definitely a lot that goes into learning serverless tech like AWS Lambda. I lead Developer Advocacy for Serverless at AWS and we're constantly loo…
-
comment
Comment #25277631
It was a long day yesterday, thank you :)
-
comment
Comment #25270810
Same as Lambda has before. The state you have is most likely short lived as we reap worker environments every so often, but in-between invokes you could persist some data in memory…
-
comment
Comment #25270667
Awesome, thanks for sharing this.
-
comment
Comment #25270553
::waves at Yuri:: Thanks! It's been a fun/interesting 4 years in this space :)
-
comment
Comment #25270537
There's no impact of this feature to how you invoke your Lambda functions.
-
comment
Comment #25270255
No good way to do this today. You are right in that you'd be forcing cold-starts. You could use a Lambda Extension to provide some sort of after-processing clean up of vars or /tmp…
-
comment
Comment #25270162
Yes, but you deploy it from one region.
-
comment
Comment #25270143
This is all based on how the RunTime API worked already (pre-dates this launch by 2 years or so). We wanted to not change too many bits. Since function code has no listening socket…
-
comment
Comment #25270095
Thanks! Appreciate the feedback and hope this helps you out. Let us know if it doesn't :) - Chris
-
comment
Comment #25269536
That is not at all what my words say and I won't reply to that thread which was started by a former competitor to troll this convo today. The perceived lock-in is really no differe…
-
comment
Comment #25269402
There's a few things at play. Functions will still stay warm inbetween invocations and will keep local any data already in the worker. We also maintain a couple different levels of…
-
comment
Comment #25269170
thar be dragons :)
-
comment
Comment #25269145
Enough that in 2019 it was the most popular topic at re:Invent (our big user conference) and that today per our re:Invent announcement almost half of all new compute workloads in A…
-
comment
Comment #25269102
The naming is a bit of a misnomer, today L@E doesn't run at the edge (in our PoPs) but when you deploy it copies to every region and then CloudFront routes you to the lowest latenc…
-
comment
Comment #25269001
Yes, either those docs will ship today or sometime this week. They are doing everything in batches but I've seen the SAM support pre-launch (which would require it). - Chris
-
comment
Comment #25268839
It me.
-
comment
Comment #25268596
Interesting. Not possible today. We'd still encourage paralyzation up through multiple concurrency of functions being executed.
-
comment
Comment #25268594
Yes, you are still limited to 15 minute maximum duration. - Chris Munns - Lead of Dev Advocacy - Serverless@AWS
-
comment
Comment #25268526
Yes, to be clear this change was just for Lambda. L@E is honestly a completely different service run by a different part of AWS that just happens to share parts of our core worker …
-
comment
Comment #25268476
Thats me. We've got some fun things we do behind the scenes to keep Lambda container image support snappy. SO yes, up to 10gb artifacts with container image support.