Y
HN Search
Hacker News Search
new
|
comments
|
top
|
jobs
munns
searching Neon…
1.
▲
2.
▲
3.
▲
4.
▲
5.
▲
6.
▲
5 ms
·
1.
▲
Cloudflare and PlanetScale launch integration
(planetscale.com)
6 points
by
munns
1y ago
|
2 comments
2.
▲
by
munns
1y ago
from the post: Combining Cloudflare Workers, Hyperdrive, and PlanetScale relational databases allows you to build modern globally distributed applications without worrying about database connection limits or latency. Your Workers run global
3.
▲
by
munns
1y ago
Thanks for that callout, absolutely right. Fixed!
4.
▲
PlanetScale for Postgres is now GA
(planetscale.com)
306 points
by
munns
1y ago
|
190 comments
5.
▲
by
munns
5y ago
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 looking at ways to help streamline and simplify this proce
6.
▲
by
munns
6y ago
It was a long day yesterday, thank you :)
7.
▲
by
munns
6y ago
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 or tmp space.
8.
▲
by
munns
6y ago
Awesome, thanks for sharing this.
9.
▲
by
munns
6y ago
::waves at Yuri:: Thanks! It's been a fun/interesting 4 years in this space :)
10.
▲
by
munns
6y ago
There's no impact of this feature to how you invoke your Lambda functions.
11.
▲
by
munns
6y ago
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 space.. but thats hypothetical I haven't s
12.
▲
by
munns
6y ago
Yes, but you deploy it from one region.
13.
▲
by
munns
6y ago
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/port as it were you need something (like the bootstrap
14.
▲
by
munns
6y ago
Thanks! Appreciate the feedback and hope this helps you out. Let us know if it doesn't :) - Chris
15.
▲
by
munns
6y ago
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 different than consuming other technologies. You make a trade-
16.
▲
by
munns
6y ago
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 cache so as to not hit ECR often. I know we've go
17.
▲
by
munns
6y ago
thar be dragons :)
18.
▲
by
munns
6y ago
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 Amazon are based on it. Pretty heavily used across different
19.
▲
by
munns
6y ago
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 latency region for your request.
20.
▲
by
munns
6y ago
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
21.
▲
by
munns
6y ago
It me.
22.
▲
by
munns
6y ago
Interesting. Not possible today. We'd still encourage paralyzation up through multiple concurrency of functions being executed.
23.
▲
by
munns
6y ago
Yes, you are still limited to 15 minute maximum duration. - Chris Munns - Lead of Dev Advocacy - Serverless@AWS
24.
▲
by
munns
6y ago
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 platform. I am not 100% aware of when they might adjust thei
25.
▲
by
munns
6y ago
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.
26.
▲
by
munns
6y ago
Yes, announced today you can go up to 10gb/6 vCPUs: https://aws.amazon.com/blogs/aws/new-for-aws-lambda-function...
27.
▲
by
munns
6y ago
Not entirely. This is something we've been thinking about for years now and is really about tooling and developer workflow. That is where the biggest benefit is for this. - Chris - Serverless@AWS
28.
▲
by
munns
6y ago
Yeah, this is Day 1 for this and I think we've got a bunch of ideas to make it easier in the future. Most importantly we're looking for feedback just like this! Thanks, - Chris
29.
▲
by
munns
6y ago
1. Sorry you are disappointed by this. 2. This is why I wanted to post here, to make it really clear. Andy only got to spend a few seconds on this and couldn't get into all the nuances. The launch post does, and we'll have more po
30.
▲
by
munns
6y ago
Couldn't share future roadmap here, but these are some cool ideas :)
More ›