One executable with cmd-line params or just many satellite executables?
Posted
by
Nikos Baxevanis
on Stack Overflow
See other posts from Stack Overflow
or by Nikos Baxevanis
Published on 2011-03-15T13:50:41Z
Indexed on
2011/03/19
16:10 UTC
Read the original article
Hit count: 275
I design an application back-end. For now, it is a .NET process (a Console Application) which hosts various communication frameworks such as Agatha and NServiceBus.
I need to periodically update my datastore with values (coming from the application while it's running).
I found three possible ways:
- Accept command line arguments, so I can call my console app with -update.
- On start up a background thread will periodically invoke the update method.
- Create an updater.exe app which will do the updates, but I will have code duplication since in some way it will need to query the data from the source in order to save it to the datastore.
Which one is better?
© Stack Overflow or respective owner