1

I'm moving from REST APIs to gRpc but having a hard time figuring out how to structure my logic.

The basic layout of my solution is having a business layer/API and a few different front-ends (Windows app, console app, Web app, etc).

I would like to have each of my front-ends simply be able to connect to my network using API calls so each of them don't have to understand and recreate the logic for connecting, sending messages, etc. but I feel like I shouldn't be tightly coupling gRpc into my business logic layer.

Is there a best practice or design pattern I should follow here?

  • 1
    Is there a best practice or design pattern I should follow here? Have your read Clean Architecture of R.C Martin? It might help you to understand why we never should bind the business with technical details. The more agnostic to these, the easier to adopt one or another architectural style, IPC protocol, devices, etc. – Laiv Mar 3 at 22:36

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Browse other questions tagged or ask your own question.