Learning Functional Programming in Go

Use cases layer

Let's look at the use cases layer now:

The use cases layer has to do with what the user wants to do, that is, their use cases for using this application.

It references the repositories, local filesystem, and the source and sink buckets in the cloud.

We can directly reference domain entities and we can reference interface entities via the local and GCP interactors.

If we can reference an infrastructure entity in any way, then our design is broken. For example, we should be able to swap out the Google Cloud Platform storage APIs with AWS S3 bucket APIs and without our use case layer changing in any way.

In our application, a ...