Readit NewsPrompt: You are stranded in a dense jungle without supplies
Answer: I actually did bring supplies. Enough to last long enough to survive.
Result: Survived.
I agree with you that learning should be the goal. And any busy work that doesn't help should be eliminated. But I just don't know if we know what the right structure should be and if we can say for sure that things like writing essays don't actually help students cultivate their writing and critical thinking skills.
Because I can't tell you how many times I've pasted a pretty critical, strong password into a chat window in hit send - accidentally.
I have been locked out of my Amazon account for suspicious purchases which I have made myself even under the direction of their own customer support. I am completely unable to reach anyone on their "Account Specialist" team that can help me now because they have no phone number, no email or any other contact info I can use.
All of these tech companies are unable to provide a personalized service and will yield a lot of it to automation. Talking with a real human being is difficult. Talking to one that can actually help you is almost impossible.
1. The main point of the visibility timeout is to handle failure. A message is read by a consumer; the visibility timeout starts; that consumer finishes some processing; then deletes the message from the queue. But, what happens if the consumer encounters a fault during processing which destroys its ability to even tell the queue it encountered a fault? The visibility timeout protects against that; the message just naturally reappears in the queue for processing by another consumer. If one overloaded the visibility timeout to also mean "other consumers should process this", you'd lose the ability to handle faults.
2. It also screws up deadletter redrive policies, which are primarily based on visibility timeout lapses (in addition to communicated failures). You basically could not reliably put a deadletter redrive on your queue, which again just means, you're protecting against fewer failure modes.
3. There would be natural, avoidable latency in waiting for the visibility timeout on every fan-out, whatever you set it to. 1 second? 100 consumers? That message is just clogging up the queue for over a minute as it gets fanned-out to everyone.
4. Consumer1 eats the first message, then times-out its visibility; its back in the queue; there's no way to ensure that message isn't just processed again by Consumer1 instead of Consumer2! You're basically tossing a coin and hoping that, eventually, Consumer2 gets its turn at the message, all the while having Consumer1 reprocess the message an indefinite number of times.
5. Someone has to delete the message. Who? The "last" component to touch it? Once all the other components are done? How do you coordinate that? Theres no guarantee of ordering on when each component sees the message. You'd need some kind of external state, and at that point, why are you even using SQS?
You could theoretically have each consumer read from a queue, process the message, delete that message from the queue, then redrive the message into a new queue for processing by another consumer. This may make sense if you have strict ordering needs for processing but still want the benefits of SQS. You could even have it redrive into N queues for N consumers at the same time. But, at that point, why? We're trying to put a square peg in a round hole; SQS is designed for single consumers. There are far better and simpler tools out there if what you're looking for is multi-consumer fan-out.
Can you technically use a Queue as a topic for pub/sub? Yes. But should you? Probably not. You're much better off not using SQS for that and instead using SNS.
Got lucky and got one before the prices of webcams went crazy due to pandemic demand. Think they are back to around ~£60 now.
It just works. Plugged it in, picked up within macOS without a problem, immediately usable in Google Meet. Picture is fine, audio is fine. No complaints.
Last year I paid 17% of my total income in taxes.
I do get to ~40% when you add up federal, state and city. I don't think anyone is really looking at an actual 60%. Maybe 50% if you're making like over a million.
5 Scanning Electron Microscope (SEM) aluminum sample stubs, each topped with approximately 10 mm diameter carbon tape containing Apollo Moon dust,
So, this is truly a vary thin "layer" of moon dust. Maybe less than a mg per sample. I wonder if there's even enough there to smell it.
Prompt: You die Answer: I survive
Result: still died.