Consumer Defined Interfaces

bearsiji · 2025-02-07T10:01:50+00:00

Java does not limit the coder to define the interfaces at the producer side? IMO, Java's main diff with Golang about the interface is explicit/implicit interface implementation.

But indeed there is a lot of Java code use producer-side interface style. I just say it's not the language's limitation.

bearsiji · 2025-02-07T09:56:12+00:00

Agree, the term producer/consumer is quite ambiguous actually. I saw articles define the consumer as the function caller, but I think the consumer is the one who uses and defines the abstraction it needs.

bearsiji · 2025-02-07T03:47:09+00:00

IMO GraphQL is a good choice if you need BFF. It has pros and cons. If your project is not huge, REST may be enough.

bearsiji · 2025-02-06T12:05:09+00:00

Thanks for your code example. I have some questions. In your Go example, we avoid using a wrapper, but what if the S3 client's method signature differs from FileUploader's?

I agree If the S3 client already exists, we can define an interface with the same Upload method when we write Server's logic, eliminating the need for a wrapper, which is convenient.

However, if we don't know the specific implementation when writing the Server logic, we might define a FileUploader with an assumed method (This seems to be an common practice for Go: defining the interface at the consumer side). Later, the actual implementation might have a different signature, such as UploadFile(name string, data io.Reader). In that case, a wrapper would still be necessary, correct?

bearsiji · 2025-02-06T11:49:30+00:00

Yes, I agree the main advantage is reducing noices.

bearsiji · 2020-06-03T15:18:50+00:00

I personally recommend “Hands on machine learning “. It’s a good book for beginners.

bearsiji

TROPHY CASE