Easy to use SQS Queue fascade

[PhilipeLouchtch]

To ease development of the lambdas, it's nice to have a single, simple interface for SQS to read and write messages to AWS SQS.

Requirements:

• [x] ability to mark messages as received only after it has been processed successfully
• [ ] make sure that no messages are returned only if the SQS queue is empty
  • naive: empty when no messages available, means having to poll and try a couple of times
  • advanced: empty when truly no messages in queue, also none "in-flight"

[TimSpeelman]

Do we need a FIFO-queue or a normal queue? Only the FIFO guarantuees one-time delivery, but at the cost of throughput. https://docs.aws.amazon.com/AWSSimpleQueueService/latest/SQSDeveloperGuide/welcome.html

[PhilipeLouchtch]

Standard is fine, won't matter much if we get a message double. Can tolerate a case that we get a message twice.

Shouldn't matter for the report, at all.

However, 3000 msgs per second is still pretty f-ing high for our purposes. Can always change which one we use later.

[TimSpeelman]

Well we could evaluate both right?

[PhilipeLouchtch]

I'd say: stick to the standard, can evaluate if time. Not sure if useful though, might ask the TA. SQS is part of our architecture but might be outside the scope of the assignment.