vladimir.rech
New member
- Joined
- Mar 27, 2020
- Messages
- 1
- Programming Experience
- 10+
Hi.
I'm working in a mission critical application and I have to create an end point that receives the parameters send to be processed some time and returns to the client application that the request was received.
The client application don't have to wait for the process result.
What is the best way to acomplish that between these options:
1. The end point fires a thread (System.Threading.Thread)
2. The end point stores data in Windows Queue to be processed by a worker.
3. The end point stores data on database to be processed by a worker.
Constraints:
1. The data sent to be processed can't be lost, it's part of a financial application.
2. The back end is a monolithic application and is distributed between 5 servers with load balancer.
3. At this moment we can't broke it in microsservices.
Thank's.
I'm working in a mission critical application and I have to create an end point that receives the parameters send to be processed some time and returns to the client application that the request was received.
The client application don't have to wait for the process result.
What is the best way to acomplish that between these options:
1. The end point fires a thread (System.Threading.Thread)
2. The end point stores data in Windows Queue to be processed by a worker.
3. The end point stores data on database to be processed by a worker.
Constraints:
1. The data sent to be processed can't be lost, it's part of a financial application.
2. The back end is a monolithic application and is distributed between 5 servers with load balancer.
3. At this moment we can't broke it in microsservices.
Thank's.