Java design pattern for abstracting out aws s3 client operations
What is the best [ most suitable perhaps! ] java design pattern that one can follow to abstract out aws s3 client connection(s)/operation(s) [ using the aws java sdk for s3 ] from the business logic layer?
Aucun commentaire:
Enregistrer un commentaire