i know Im asking randomly but does someone know a tool to get back into an instagram account?? I was stupid forgot my login password. I would love any tips you can offer me!
@Kingston Malakai Thanks for your reply. I found the site thru google and Im in the hacking process atm. I see it takes a while so I will get back to you later when my account password hopefully is recovered.
Doubt in the FIFO Queues: What happens when a message(of a particular group) has been successfully processed by a consumer, after which the consumer goes down before sending the delete Message call SQS? Won't SQS make the same message available to be consumed and processed by another consumer? Thereby violating the requirement of not processing duplicates?
Yes you would get the message again after the visibility timeout, so it's best to develop your consumer for idempotency (detect if the operation is a duplicate one) in case they're down and cannot delete the message. have a look at the last section in the docs here: docs.aws.amazon.com/AWSSimpleQueueService/latest/SQSDeveloperGuide/FIFO-queues-understanding-logic.html
I think with FIFO deduplicationId it's only used to prevent duplicate message to be accepted by SQS FIFO queue from producer only within a deduplication interval. For consumer level deduplication we have to somehow use some logic to deduplicate at consumer end.
Best explanation about queues!!! It would have been great if Amazon MSK use case was included.
Very well explained. A good handover between the use case sessions and the demos. Thanks for this session.
i know Im asking randomly but does someone know a tool to get back into an instagram account??
I was stupid forgot my login password. I would love any tips you can offer me!
@Jude Caspian Instablaster =)
@Kingston Malakai Thanks for your reply. I found the site thru google and Im in the hacking process atm.
I see it takes a while so I will get back to you later when my account password hopefully is recovered.
@Kingston Malakai It worked and I finally got access to my account again. Im so happy:D
Thanks so much you really help me out !
@Jude Caspian Glad I could help xD
This is a gem
Doubt in the FIFO Queues: What happens when a message(of a particular group) has been successfully processed by a consumer, after which the consumer goes down before sending the delete Message call SQS? Won't SQS make the same message available to be consumed and processed by another consumer? Thereby violating the requirement of not processing duplicates?
Yes you would get the message again after the visibility timeout, so it's best to develop your consumer for idempotency (detect if the operation is a duplicate one) in case they're down and cannot delete the message. have a look at the last section in the docs here: docs.aws.amazon.com/AWSSimpleQueueService/latest/SQSDeveloperGuide/FIFO-queues-understanding-logic.html
I think with FIFO deduplicationId it's only used to prevent duplicate message to be accepted by SQS FIFO queue from producer only within a deduplication interval. For consumer level deduplication we have to somehow use some logic to deduplicate at consumer end.
Fantastic explanations and demos!
Kuba, wyjazd do Kanady dodał Ci skrzydeł :) Gratulacje
Fiu fiu fiu, gratulacje Kuba!
Excellent Session
So clear. thanks.
Amazing talk!
Are they teaching us how queues work or what? I don't see how these queues differ from RabbitMQ
Much needed enlightenment..
First!