❔ Vertical Slice architecture + gRPC
I wish to organize a server that communicates with its clients via gRPC using the Vertical Slice architecture.
I see this architecture as a nice fit for my development needs, as it groups everything nicely into features.
Let's assume the server handles two domain contexts:
- identity: users, roles
- store: products, categories
As I'm still soaking in the concepts, I find it difficult to understand how to correctly apply this architecture when using gRPC instead of REST.
Give that proto files define endpoints and 'models' exchanged via said endpoints, how should I correctly structure the proto files in the project structure?
The proto files would then have to be referenced by client applications.
The second part is understanding how to structure the client applications if I also want to group by features + reference the server proto files. In addition, I wish my clients to be modular - extensible via runtime loaded plugins that provide extra features.
----------------
I have made some attempts here and there; however, I wish to ask this question from a clean slate and try create something based on your suggestions.
4 Replies
You'd be better off giving some examples and asking choice 1 or choice 2. Your question is too subjective and abstract
^
You're right...
Was this issue resolved? If so, run
/close - otherwise I will mark this as stale and this post will be archived until there is new activity.