https://github.com/meysamhadeli/chat.application
Implementing chat application wit .net core and allows you to send/receive text messages with other users
https://github.com/meysamhadeli/chat.application
chat docker dotnet dotnet-core dotnetcore messaging nats vertical-slice-architecture
Last synced: 5 months ago
JSON representation
Implementing chat application wit .net core and allows you to send/receive text messages with other users
- Host: GitHub
- URL: https://github.com/meysamhadeli/chat.application
- Owner: meysamhadeli
- License: mit
- Created: 2021-11-09T14:42:30.000Z (almost 4 years ago)
- Default Branch: main
- Last Pushed: 2022-07-31T08:20:07.000Z (about 3 years ago)
- Last Synced: 2025-03-31T18:51:48.390Z (7 months ago)
- Topics: chat, docker, dotnet, dotnet-core, dotnetcore, messaging, nats, vertical-slice-architecture
- Language: C#
- Homepage:
- Size: 130 KB
- Stars: 7
- Watchers: 1
- Forks: 3
- Open Issues: 0
-
Metadata Files:
- Readme: README.md
- License: LICENSE
Awesome Lists containing this project
README
# Chat Application
## How To Run
For running Nats message broker in your system you can use of this [docker compose](./deploys/compose/docker-compose.yaml) file.
For running our system we need to run our [Console Application](./src/Chat.Console) as client and [API](./src/Chat.Api) as a service. we can use bellow command in root of project with shell to running our clients and api. Our api will up and running on this `http://localhost:8000` address.
``` cmd
.\scripts\backend-api.bat
.\scripts\console-ui.bat
```
we can create multiple instance of console application as our chat UI and we can chat between these separated console instances, we have to run `.\scripts\console-ui.bat` multiple to create multiple instance of chat application.
## Chat Architecture Diagram
In above diagram I show how our components connect together for running this chat application. Here we have two console application or two instance of console application as our Chat UI, one NATS message broker and one API service for get and post some data.
The flow of our application is like this:
- Our first console application (instance 1) as Chat UI sends a message data to our API service.
- Our API endpoint will get posted message from the client and process and save this message in a in-memory storage (EF-Core In-memory) and then publish this message as a event to our NATS message broker. This message contain needed information for our subscribers for example `sender` , `receiver`, `message` and our subscribers can pick their needed information from theses events.
- Our second console application (instance 2) as Chat UI, that is subscribed to that event through our NATS message broker, receives this message from the broker and will show on the console.
## License
This project is made available under the MIT license. See [LICENSE](https://github.com/meysamhadeli/Chat.Application/blob/main/LICENSE) for details.