Видео

haha, thank you!

AFAIK timestream doesn't give you a data change stream that you can subscribe to, so you'd have to create your own. How are you getting the data that you write to Tiemstream? Do you get them as a S3 file?

@@theburningmonk i have aws iot topic captured by a kinesis data stream. The kinesis data stream trigger a lambda function which is responsible for dumping data into timestream database.

Thanks! I've been stung by Amplify CLI too, but I heard gen 2 is much better. I haven't tried it out myself yet, so I will reserve my opinions for now. What would you say were the biggest problems with Amplify CLI?

Thanks, glad you liked it!

Thank you, glad you liked it!

Glad you like it!

Agree :-)

Thank you :-) Glad you liked it!

Thank you :-)

Conceptually they're different things. Events and commands are used to model your system's behaviour and their interaction, and a Lambda function is used to carry out some business logic in response to an invocation request. In your example, the invocation event might be a "command", if the event carries a message that requests some action to be performed. But Lambda functions can be invoked in response to an event too. Commands often follow a request & response pattern, but not all request & response communications are related to processing commands.

Glad you enjoyed it!

thank you, glad you liked it!

Glad you liked it

Thank you, glad you liked it!

She totally is!

thanks!

Glad you liked it!

This is a preview lessons from my course, the "next lesson" it refers to is part of the course but I haven't released it on RUclips. I've added a link to the full course in the description instead.

Thanks Khawaja! It was one of my fav episodes as well

Thank you for the summary and glad you enjoyed it!

Thank you!

For a more nuanced discussion discussion about lock-in, have a watch of Gregor Hohpe's talk about the different dimensions of "lock-in" and understanding the cost of avoiding "lock-in" ruclips.net/video/Ud9h1hJgoKk/видео.html He also has a good article too "Don't get locked up into avoiding lock-in" if you're interested in a different perspective. martinfowler.com/articles/oss-lockin.html

I think you can still use the open source version, right?

My pleasure!

I'm thinking of doing it for the Production-Ready Serverless workshop (productionreadyserverless.com/) in May, but it'd be pretty high level though. Because a) I haven't used it much myself, and b) some of the new features like IAM enforcement is only available on the paid plans (there is a 14 day free trial, but that's not enough for the length of the workshop)

maybe, I haven't used it enough myself though, so might not be the best person to do it

@@theburningmonk noo no, we only trust you to teach this, WTB course

thanks, glad you liked it!

Tell me more?

I like Ben Kehoe's definition of serverless being a spectrum: ben11kehoe.medium.com/the-serverless-spectrum-147b02cb2292 with that in mind, Fargate is more serverless than EC2, but not as serverless as Lambda because it doesn't scale to 0 and does not offer usage-based pricing, two of the litmus tests for "fully serverless" services: www.gomomento.com/blog/fighting-off-fake-serverless-bandits-with-the-true-definition-of-serverless That's not to say that Fargate might not be a bad option for Fathom, but it's definitely not as hands-off as Lambda, which is what the Fathom team is looking for from what I gathered.

Was great to have you on the show, loved the insights into the streaming side of things!

Glad you liked it. It's one of my fav episodes so far as well. There's a lot of really interesting technical challenges that goes into video streaming at scale, it's under-appreciated

It's not that cold starts are more spikey, but when you have sudden spikes in traffic, cold starts is more likely to be a concern. With the introduction of proactive initialization (see aaronstuyvenberg.com/posts/understanding-proactive-initialization) most cold starts will really impact users - e.g. when you do a deployment in the middle of the day, or when existing workers are replaced. But if you have a sudden spike in traffic, then you need more workers to handle the load, so Lambda would need to create new execution environments on-demand, and you'll see lots of cold starts in that moment. An example would be a social network, when a popular user posts something, suddenly everyone logs in and start interacting with the app. You can't plan for these kinds of spikes.

Glad it was helpful!

When you either 1) can't use Lambda because - e.g. you need to run for more than 15 mins, or 2) it doesn't make economic sense to use Lambda in TCO terms - e.g. when you have a high throughput API (say, averaging 1000+ RPS) and you have a team that knows how to run containers at scale. The TCO bit is important, because it depends on whether you need to hire additional skillset into your organization. If you do, then that makes massive difference, and that's why Jack said in the video that, it'd only make sense for them to containerize if the cost of Lambda reaches 2-3 full-time devops engineers, because that's probably the minimum you'd need to operate a containerized environment 24/7.

Same topic, focused on AppSync: Is an HTTP resolver to a payment API, for example, capable of handling 1000 transactions per second? I purchased your AppSync course and want to implement it where I work.

Always check the quotas page for the service you want to use. They might not be exhaustive but it's a good starting point. You can do it by googling "<service name> quotas" or go to the "Service Quotas" console in your AWS console. For AppSync specifically, you're looking for this page: docs.aws.amazon.com/general/latest/gr/appsync.html In terms of throughput, you're concerned about the "Rate of request tokens", which roughly translates to 2,000 RPS but that's a soft limit and can be raised. There might be a hard limit somewhere, but it's likely much higher than the 2,000 RPS default limit.

The closest approximatation is the initDuration, which is reported in the Lambda REPORT logs, but is not a metric. You can analyze it with CloudWatch Logs Insights. There are also some other time associated with downloading the artefact, and allocating a space in the fleet. But those are outside of your control, so it's best to focus on the initDuration, which is how long does it take to initialize the execution environment on a worker instance.