ex_aws VS exq

If you want to upload files from the server, please check out ex_aws, ex_aws_s3, and AWS S3 in Elixir with ExAws. Uploading from the server is very straightforward compared to uploading from the client mainly because ex_aws already includes all necessary request settings. If you want the user to first upload the file to the server (maybe you want to change the file a bit before storing it or generating thumbnail of the picture), then consider also using Waffle that comes with seamless integration with ex_aws.

We will use the library ex_aws to manage all the AWS resources

AWS: I don't have a definitive answer for you on AWS. I've used ex_aws a good bit, and it's reasonably solid. aws-elixir also seems to be actively maintained.

Prepare your account, we will use AWS_ACCESS_KEY_ID and AWS_SECRET_ACCESS_KEY. Please visit here for more information about ExAWS: https://github.com/ex-aws/ex_aws

- https://github.com/ex-aws/ex_aws

Oban, backed by PostgreSQL or SQLite, also provides a queue-based job processing system. Exq, on the other hand, is backed by Redis. It provides features similar to Flume, but without built-in rate limiting and batch processing capabilities.

Enter Oban, which leverages Postgres' notify/listen functionality to provide a durable queue. Oban is solid and doesn't require Redis, which is cool. I end up using this in most projects I work on. If you absolutely need the speed of Redis, Exq is a pretty good option.

Job processing libraries compatible with Sidekiq, for example exq, won't deserialise your Dry::Struct arguments. This is most likely an acceptable tradeoff.