may i ask you a question about AWS certificate? A company has a web-based order processing system that is currently using a standard queue in Amazon SQS. The IT Manager noticed that there are a lot of cases where an order was processed twice. This issue has caused a lot of trouble in processing and made the customers very unhappy. The manager has asked you to ensure that this issue will not recur. What can you do to prevent this from happening again in the future? (Select TWO.) A, Replace Amazon SQS and instead, use AWS Step Functions. B, Use an Amazon SQS FIFO Queue instead. C, Alter the retention period in Amazon SQS. D, Alter the visibility timeout of SQS. E, Change the message size in SQS. The answer is A,B. Why the Step Function could help to fix SQS send messages twice time?
As the requirements naturally change over time, the simplicity of this step functions (aka bpm tools) will also suffer from complexity and maintenance problems. Seeing too complex sequence diagram on ui tool doesn’t make it easier to work with. Thanks for explaining it
I believe that we should keep the visual diagrams as a higher level view of the system without much actual business logic code. Similar to level 3 component diagram in c4 model. These tools are not capable of maintaining complexity like modern programming languages because of lacking refactoring techniques and tools. So they shouldn’t handle all details.
Get my Step Functions Masterclass Course here: bit.ly/sf-masterclass-course
Really great, as usual, Daniel. Thank you so much for giving us your time and knowledge. 🤗
Its awesome, the way you explained about Step Functions is excellent. I also using this service in aws. Pls do/share vedios on sagemaker.
I’m not fully ‘there’, but when I do arrive at full AWS understanding & practicality it’ll be due in part to your concise instruction.
may i ask you a question about AWS certificate?
A company has a web-based order processing system that is currently using a standard queue in Amazon SQS. The IT Manager noticed that there are a lot of cases where an order was processed twice. This issue has caused a lot of trouble in processing and made the customers very unhappy. The manager has asked you to ensure that this issue will not recur.
What can you do to prevent this from happening again in the future? (Select TWO.)
A, Replace Amazon SQS and instead, use AWS Step Functions.
B, Use an Amazon SQS FIFO Queue instead.
C, Alter the retention period in Amazon SQS.
D, Alter the visibility timeout of SQS.
E, Change the message size in SQS.
The answer is A,B. Why the Step Function could help to fix SQS send messages twice time?
As the requirements naturally change over time, the simplicity of this step functions (aka bpm tools) will also suffer from complexity and maintenance problems. Seeing too complex sequence diagram on ui tool doesn’t make it easier to work with. Thanks for explaining it
I agree with you I think, but can you state what you think is the remedy for the problems that you mentioned?
@oacargil Can you please explain how can we resolve those issues as you mentioned in case of complexity
I believe that we should keep the visual diagrams as a higher level view of the system without much actual business logic code. Similar to level 3 component diagram in c4 model.
These tools are not capable of maintaining complexity like modern programming languages because of lacking refactoring techniques and tools. So they shouldn’t handle all details.
That's still better than having no diagrams. Moreover, if it becomes too big, we can always combine step functions.
the coin base is the biggest bit coin in a crypto currency
Gross, talk about burying your business logic in the most obscure place if you use these.