I want to understand why I need to use temporal activities instead of writing a retry logic myself as shown below.
- One thing I can think right of the bat is, temporal activities are more cleaner code than the while loop.
But is there anything to temporal activates advantage apart from that?
Let’s not bring in statefullness workflows offer and the advantages it can bring in to the activities. Let’s talk purely in the context of activities.
FYI : I’m conducting a Brown Bag session. First I’m going to show the above code and explain how we can implement retries and make our applications more resilient. Then I’m going to show temporal activities. And I need few points to highlight the advantageous of activities against self written retry logic.