Open ckhsponge opened 4 days ago
Interesting. I had a dream (or nightmare) last night about splitting out features of aws-sdk-rails into separate gems. I originally made that decision some years ago to drive usage and make maintenance easier but it's actually been the opposite. I think it would be backwards compatible to pull it out, have the lastest aws-sdk-rails depend on it, and maintain multiple gems in the aws-sdk-rails repo. If you'd like to share that work, we can track it here, but no guarantees on timeline. @alextwoods @jterapin thoughts?
I like that I idea. I can try to get a PR put together.
Thanks for creating SqsActiveJob! I've tested it and it seems to work well.
My feature request is to split SqsActiveJob into it's own gem and remove the dependency on Rails. The ActiveJob gem does not require Rails. Lambdas can run Ruby. A lightweight Lambda could have a few gems not including Rails and be very effective at background job processing.
I've tested the project after removing 3 Rails references:
I'd be happy to split this project out myself however not maintaining it in 2 places would be better.