Discord.NET in microservice architecture?

[Misha12]

Is there any way to share DC.NET entities between multiple applications in microservice architecture?

For example, I want to have 1 application (bot) that keeps connection with a discord, cache, or something else. This bot will have defined some commands for some feature. This feature will have business logic in another service. Is there a way to send some DC.NET entities (Guild, Channel, User, ...) to another service without having to convert to my models or download these entities from the discord api?

[EddieDemon]

Sure, the client application will function as a gateway. So it'll receive and send messages from Discord where your application will forward the request to the appropriate services. Please take note on the required 3 seconds response time or defer the request/response.

[Waterball12]

Probably wants something like

Discord - > - Gateway - > - Worker (Command Handler) - > - Some microservice 

D.Net doesn't seem to be suitable for a microservice architecture, I rather look at Remora. But if you already have to pass D.NET entities around probably your architecture need to reconsider how to deal with them?

[ginomessmer]

Agreed. I would bring OP's ubiquitous language into question if they really want to reuse D.NET's entities. Perhaps make it more specific to your domain?