munns

9 ms·

31.
by munns 6y ago
+1. That's the idea. Run any container in Fargate. Now use the same tools you use to build/package those containers in Lambda.
32.
by munns 6y ago
No to be clear I'm saying you are comparing things that are way more different than our friends at Cloudflare would like you to think. They aren't brought up in any of the convos I have with customers.
33.
by munns 6y ago
Yes. But being real, we hear you on this one. I can't comment on API Gateway's roadmap here but this is something both teams is aware of. The reason it is the way it is today is for a valid reason. But this is def something we hea
34.
by munns 6y ago
Except that none of the rest of your infrastructure is there, and that APIs represent just a non-majority part of Lambda workloads.
35.
by munns 6y ago
Today, for a nonstop workload you might save money with Fargate or ECS.
36.
by munns 6y ago
Hey everyone, we're really excited about this feature launch, and I wanted to come in to clarify any misconceptions. With this capability you can now package Lambda functions using familiar container image tools (Dockerfile, cli tools,
37.
by munns 6y ago
Awesome! That was the idea here. Lots of sub 100ms workloads and we really want you to be able to pay for what you use. - Chris, Serverless@AWS
38.
by munns 6y ago
A lot of this was based around the fact that we've seen languages become just so much more performant. This includes Go/Rust/etc, but a lot of Node.js workloads are also sub 100ms, or fast enough that they'd benefit from
39.
by munns 6y ago
You are billed by the execution time of the function. So from the millisecond we hand the event over to you until you return a response or timeout. - Chris - Serverless@AWS
40.
by munns 6y ago
How long would you like it to be? Chris Munns - Lead of Dev Advocacy for Serverless@AWS
41.
by munns 6y ago
This is however a soft-limit per region
42.
by munns 7y ago
Thank you for clarifying! I know quite a lot has supposedly shifted. Will update my original comment.
43.
by munns 7y ago
Fwiw: Slack, Lift, AirBnb, Snapchat, Stripe are all 100% public cloud based (in so far as I know). So up through 8+ figures they are still doing it too. removed Uber as its not 100% cloud (or at least wasn't in the past)
44.
by munns 7y ago
On your own metal it looks like it does in this post. With managed services it looks a world different.
45.
by munns 7y ago
As the original creator of the presentation referenced by the blog author (later re-delivered by Joel in the linked post) I am super excited to see this still have an impact on people, but I'd say today in 2019 you'd probably do t
46.
by munns 7y ago
Dollar to dollar comparisons are one way to compare these two technologies but it leaves a lot not covered. The application programming model varies greatly (socket/port vs. event). There's also a lot more that Lambda brings to th
47.
by munns 7y ago
We've just published a second post on this launch: https://aws.amazon.com/blogs/compute/new-for-aws-lambda-pred...
48.
by munns 7y ago
Fwiw new networking for VPC is completely rolled out for all public regions now. (#2) (and thank you, its called "Attached to a VPC" and not in :) ) This covers you straight through 4. Now it's possible that your execution en
49.
by munns 7y ago
Hey all, I lead developer advocacy for serverless at AWS and was part of this product launch since we started thinking about it(quite some time ago I should say). I'm running around re:Invent this week, but will try and pop in and answ
50.
by munns 7y ago
Miles and I know each other, what's wrong with a friendly hug? Do you need a hug hesburg?
51.
by munns 7y ago
No. I've been at AWS for over 7 years in a few different roles. Came to the serverless space >2.5 years ago because I felt passionate about it (could have literally done almost anything). Again, sorry for mis-posting under my older
52.
by munns 7y ago
Hug back at ya big guy!
53.
by munns 7y ago
Yup! Haven't done it in years and created this different account to be more clear/direct in who I am. That is also why I called it out at the start and bottom of all my responses. Thanks, - Chris Munns - AWS - Serverless - https:
54.
by munns 7y ago
The issue of the application artifact size is definitely real and it blocks some NLP/ML workloads for sure. Consider that a today problem that isn't hard in Lambda. But we've 100% got customers doing near realtime streaming
55.
by munns 7y ago
and I totally posted this from the wrong account... sigh.. this is me. Thanks, - Chris Munns - AWS - Serverless - https://twitter.com/chrismunns
56.
by munns 7y ago
and I totally posted this from the wrong account... sigh.. this is me. Thanks, - Chris Munns - AWS - Serverless - https://twitter.com/chrismunns
57.
by munns 8y ago
Amazonian who has lived in Manhattan the past decade. The two neighborhoods I've lived in over the past 5 years have seen 20-30% increases: Chelsea and Upper East Side. Not sure that folks are seeing minor in Brooklyn either.
58.
by munns 8y ago
+1 on this. The paper doesn't really address the most typical usecases of Serverless which are typically API backends, streaming data processing (feeding off Kinesis/Kafka/similar), and reactions to one off-ish events like ob
59.
by munns 8y ago
I wrote the first version of this deck back in 2013: https://www.slideshare.net/AmazonWebServices/scaling-on-aws-... and it since then went on to become one of the most delivered talks by AWS across the world. I though
60.
by munns 8y ago
Roger that! Thanks!

More ›