One very good application of SFNs is if you need to delay a Lambda execution. Put a Wait task before a Lambda:Invoke task and you have it. You need jitter? Add a Pass task before the Wait and make it output waitTime = States.MathRandom(0, 30), then use waitTime as a source for the Wait task.
Good One. Can we look at some cost efficient architectures and suggestions you make to customers day in and day out. What sort of pitfalls, hacks are there to make your architecture more cost effective. Some use cases around these would help. Thanks & Regards
Hey, thanks for the video! I'm really curious on how you would design your SAGA state machine to guarantee the rollback in case of failure of one of the inner action of the parallel block that you mentioned in 08:32 (Check Address, Verify Identity Documents). The state machine presented in 09:55 presents a solution for sequential steps only. E.g. What happens if the address is checked and I save something in a DynamoDB, but my Verify Identity Documents fail? How do I know I should run a compensating action for Check Address?
Hey Gran, so the step that writes to DynamoDB should return an ID of some sort, you add that ID to the common state, and you build a new step "reconciliation" that gets triggered if an error happens. The reconciliation step uses the DDB ID that was passed to it in the state and can then delete that item from the table. Does this make sense?
This is a great intro. But I'm curious to see how you can evolve this when your states are not pre-defined. e.g think about an app like turbo tax - where your flow transitions are dictated by what you've answered previously. And it can get complicated if there are user/customer specific steps that the state machine have to take into consideration e.g. if the user navigating this flow is a premium user, then prompt the user to the 'Concierge' service step before proceeding to the ReserveFlight step
Awesome video! The pattern I would wanna see next vid is scenarios that you have solved involving chattiness (protocols, caching, or auditing) and how you would came to the solution.
i've loved the SAGA pattern since learning about it. however, i never did manage to find out what SAGA stands for lol. As for pattern suggestions, can you cover anti-patterns or, perhaps, patterns that are good but that turned out not to be great in a serverless framework? I work primarily with serverless technologies and, when I architect, I go straight for serverless designs. However, I do wonder if I'm trying to force every problem to be solvable by the same tool (serverless). Also, I'm afraid I just don't know the names of the serverless patterns and, so, can't suggest ones for you to cover.
I have no idea what SAGA stand for either haha, I just tweeted asking for it, let's see if someone can enlighten us with an answer. Covering anti-patterns is a great suggestion, I'll look into it! You're right in your reasoning: Serverless is not the solution for everything. Recursive calls, long running processes, batch processing, to name a few, are a to avoid - which gives me an idea for an episode: I'll do some digging and present some use cases that are not suited for Serverless. Hope this can help!
I have decided to Go for AWS as my career after I finish my bachelor's degree. I have learned html, css and basics of JavaScript. Should I directly start learning aws or complete my web development knowledge.Pls help me with the path what should I do first and what not? (I will be doing my bachelor's degree)
Great news, AWS Step Functions new drag-n-drop workflow editor is out: aws.amazon.com/blogs/aws/new-aws-step-functions-workflow-studio-a-low-code-visual-tool-for-building-state-machines/
![[ ออกกอง ] วัยหนุ่ม 2544 โลกหลังลูกกรง..ทัวร์กองถ่ายหนังใน "คุกของจริง" | JUSTดูIT.](http://i.ytimg.com/vi/vB--aOkZCpw/mqdefault.jpg)
Thanks!
One very good application of SFNs is if you need to delay a Lambda execution.
Put a Wait task before a Lambda:Invoke task and you have it.
You need jitter? Add a Pass task before the Wait and make it output waitTime = States.MathRandom(0, 30), then use waitTime as a source for the Wait task.
Good One. Can we look at some cost efficient architectures and suggestions you make to customers day in and day out. What sort of pitfalls, hacks are there to make your architecture more cost effective. Some use cases around these would help. Thanks & Regards
Yes, definitely - I'll think about a way to incorporate this
Thanks for this. Did you ever do a deeper dive as promised ?
Not yet, unfortunately, it's still in the pipeline though
Hey, thanks for the video! I'm really curious on how you would design your SAGA state machine to guarantee the rollback in case of failure of one of the inner action of the parallel block that you mentioned in 08:32 (Check Address, Verify Identity Documents). The state machine presented in 09:55 presents a solution for sequential steps only.
E.g. What happens if the address is checked and I save something in a DynamoDB, but my Verify Identity Documents fail? How do I know I should run a compensating action for Check Address?
Hey Gran, so the step that writes to DynamoDB should return an ID of some sort, you add that ID to the common state, and you build a new step "reconciliation" that gets triggered if an error happens. The reconciliation step uses the DDB ID that was passed to it in the state and can then delete that item from the table. Does this make sense?
This is a great intro. But I'm curious to see how you can evolve this when your states are not pre-defined. e.g think about an app like turbo tax - where your flow transitions are dictated by what you've answered previously. And it can get complicated if there are user/customer specific steps that the state machine have to take into consideration e.g. if the user navigating this flow is a premium user, then prompt the user to the 'Concierge' service step before proceeding to the ReserveFlight step
Keep further .. !
Awesome video! The pattern I would wanna see next vid is scenarios that you have solved involving chattiness (protocols, caching, or auditing) and how you would came to the solution.
Sounds good! I have the two next patterns ready to go, but I'll think about a couple for what's coming next
Thanks you for the efforts
My pleasure
Thank you ilyas for this usefull content, I just have a question even its out of context, what music name u used in the outro ?
Thank you John ! The music is called "Bounce" by Simon Petterson
i've loved the SAGA pattern since learning about it. however, i never did manage to find out what SAGA stands for lol.
As for pattern suggestions, can you cover anti-patterns or, perhaps, patterns that are good but that turned out not to be great in a serverless framework? I work primarily with serverless technologies and, when I architect, I go straight for serverless designs. However, I do wonder if I'm trying to force every problem to be solvable by the same tool (serverless). Also, I'm afraid I just don't know the names of the serverless patterns and, so, can't suggest ones for you to cover.
I have no idea what SAGA stand for either haha, I just tweeted asking for it, let's see if someone can enlighten us with an answer.
Covering anti-patterns is a great suggestion, I'll look into it!
You're right in your reasoning: Serverless is not the solution for everything. Recursive calls, long running processes, batch processing, to name a few, are a to avoid - which gives me an idea for an episode: I'll do some digging and present some use cases that are not suited for Serverless. Hope this can help!
@@WinTheCloud Thanks! Hopefully, someone knows :)
I have decided to Go for AWS as my career after I finish my bachelor's degree. I have learned html, css and basics of JavaScript. Should I directly start learning aws or complete my web development knowledge.Pls help me with the path what should I do first and what not? (I will be doing my bachelor's degree)
Learn boto3 and python
@@kellymoses8566 thanks
@@tejasgaware8234 with boto3 you can make some really cool stuff with AWS remarkably easily.
@@kellymoses8566 thanks I will surely do it
Great news, AWS Step Functions new drag-n-drop workflow editor is out: aws.amazon.com/blogs/aws/new-aws-step-functions-workflow-studio-a-low-code-visual-tool-for-building-state-machines/
Awesome Video. Very informational. I am very interested in a WebHook pattern if you can cover that.
Noted! It's already part of the plan ;)
@@WinTheCloud Can't wait! :)
👏👏👏👏👏
Are you uploading a new video every week ?
I'll try, although no promises ^^
👏👏👏👏👏