I have code that takes messages from a queue and does work. The work is mostly I/O bound. I need to be able to scale the number of workers.
I can write an application that manages threads or uses TPL to scale and manage the workers. This works but overtime has proven to be a bad approach on many fronts.
Comparing these 3 options is it possible to rank them in terms of how much resource they consume for the same amount of workers?
1) write a simple application and run many instances.
2) deploy the simple application in Service Fabric and scale it.
3) do something similar to 2) with Kubernetes.
Do others use this approach?
I know there are other factors but I'm focused on the resource usage comparison.