Drop graphql-upload

[cerinoligutom]

The upload feature via the GraphQL layer demonstrated currently in this boilerplate is really just to show an example that it is possible to do it via GraphQL. However, there have have been people using this boilerplate for their production apps reaching out to me and asking clarifications regarding how to handle file uploads at scale which in any case, I always end up recommending not to use graphql-upload if they have plans to scale. Apollo has a blog post about the topic and I highly recommend you to read it and go with Option 1 or 2 described there.

This boilerplate currently uses Option 3 which is not recommended. The original motivation for having this in the boilerplate was to show a working code for a file upload feature applied on a layered architecture with an opinionated folder structure along with GraphQL Code Generator. See singleUpload and multipleUpload mutations.

With that said, I'll be dropping the file upload feature and link the blog post as a tip instead. I won't be adding an opinionated way of handling file uploads as that is dependent on the implementation details of the 3rd party service and I don't want to lock this boilerplate to a specific service.