Hi Adron,
Thanks for starting the discussion!
For our situation we have a number of .NET console apps, some of which are waiting on RabbitMQ to give them work, some are waiting for scheduled times and some are polling the database periodically looking for work.
So for us at least, the ability to run console apps would be ideal. We have no desire to run background tasks as Windows services or as Cloud Foundry services.
In terms of status we would simply want to make sure each console app is running, so for each instance of the app to make sure there is a process running on a DEA somewhere. If the process crashes/exits then the app would be offline. It should be the developers responsibility (for now at least) to keep their process alive e.g. no need for built in scheduling etc.
In terms of deployment if we could push, configure, scale and bind services to these background apps, just like any other current Cloud Foundry app we would be happy.
Thanks,
Tyler