From someone who is working on this field, I do agree that we are collecting huge and unimaginable amount of personal customer data - and continuously transmit them to cloud via TCU which has persistent internet connection. But there is still some time for the (western/traditional) OEMs to catch up. They have so much data but have no idea what to do with it. Most of the times, it just stays there doing nothing and OEMs have no idea about it.

On the other hand, Chinese OEMs are very saavy in this area. They know what to do with your data (Mobile phones background helps a lot here) and they're doing everything they can to get an edge over all other OEMs. This is why the industry has been going towards "who has the best tech and apps" instead of "who gives safest chassis and better engines/gearboxes"

In a lawless world, I'd like to show them hell!

When I saw the name, I immediately thought of https://omnomchocolate.com/

Keeping questions from scale & benchmarks aside, this is a cool thing for functional/unit testing module that uses SQS, instead of dumb mocks.

Thank you! Yes, you should definitely use this instead of localstack :)

Although I wouldn't recommend using LocalStack's SQS implementation for production workloads, calling it a dumb mock is a bit outdated. It emulates pretty much every SQS behvaior including long polling, delayed messages, visibility timeouts, DLQ redrive, batch send/receive, ...