#Amazon file storage download

However, in order to have something that works reliably and handles all the edge cases, you have to deal with caching, redundancy, interrupted uploads and recovery, large files, timeouts, brute force and DDOS, special characters in parameters, permissions and IAM, and dozens of other pretty things. You may imagine that you can draft one in a few hours, which is true. Not only there is no added value to the intermediary service, but its cost is rather prohibitive. Any other service could easily access S3 directly, given that S3 is itself a service (it is not your service, but that is irrelevant here).

In your case, you add no value through the service. That logic is, in turn, the reason for the service to exist. How does file-management-microservice in commercial application might look like according to good design-pattern rules ?Ī goal of a service in SOA is to perform some logic which, otherwise, would have to be duplicated among other services. Thus let's assume that there is multiple tables in the file microservice, and both their structure and microservice logic are advanced. I believe in commercial/big projects design might have similar assumptions/foundations.

How could I do that in a better way ? (don't want to store files (content) on the machine where application is running ).

Is it a clean/good-design-patterns-compliant approach ?.

Uploading to cloud would be in a different thread, asynchronously and maybe even with a messagebroker help.

send meta-info back to the microservice A that initialized upload operation.

it adds: INSERT INTO file (url, name, size, type, extension) VALUES ('', 'picture', 34233, 'FILE', 'JPG')

saves meta-info about that file in a local table called file.

sends the file to a cloud storage f.e.

server does validation, secuirty check etc.

a microservice A sends an image: user_attachment.jpg to the files microservice upload endpoint.

store meta-information about the file in the file table.

create db only for that microservice with the file table.

#Amazon file storage download

at the beginning would have only two basic endpoints upload/ download a file (used by other microservices, not by a user directly).I would like to create a microservice just for files, which:

I'm creating a spring application just for learning purposes.