1 Antwort
- Neueste
- Die meisten Stimmen
- Die meisten Kommentare
0
It's the same answer as with all other SDKs: Store the object in S3 and then send a message in SQS with the location of the object. The documentation talks to this but unfortunately only Java has a pre-built library for this function; in other languages you need to do some coding - but the logic is the same.
Relevanter Inhalt
AWS OFFICIALAktualisiert vor einem Jahr- AWS OFFICIALAktualisiert vor 2 Jahren
- AWS OFFICIALAktualisiert vor einem Jahr
- AWS OFFICIALAktualisiert vor einem Jahr
Thanks for your reply, the java extended library comes with the necessary apis for handling large messages. I was looking if similar library is available for node js. Looks like it is not. But its strange that SQS is so limited with the size of the message. As a queuing service it should allow to handle large messages.
SQS is designed to support very high message rates - check out the statistics from Amazon Prime Day where SQS delivered over 70 million messages per second at peak. At that rate, having a maximum size message helps with scalability. 256 kB isn't a small message - it's only small if you're trying to pass around files. The issue with having a larger limit is that there is always going to be a case where you need "just a little bit more". So better to deal with large objects using a system that is designed to deal with that - such as S3.