Databases
StackOverflow2013
Postsdbo
POScheduler tasks registration design
 

Note that there are some explanatory texts on larger screens.

plurals
  1. POScheduler tasks registration design
    primarykey
    data
    text
    <p>I have an architectural question.</p> <p>Let's say we have a scheduler and a number of subsystems. Some of these subsystems can have actions, that should be able to be executed by scheduler.</p> <p>We have two ways to implement this registration of scheduler tasks.</p> <p>One way is to have a method in each subsystem, called like <code>RegisterSchedulerTasks</code>, that will be called by bootstrapper in application during application start. In this method we will call something like static <code>Scheduler</code> class like this:</p> <pre><code>void Handler1(){ } void Handler2(){ } void RegisterSchedulerTasks() { Scheduler.RegisterHandler( "E1", Handler1 ); Scheduler.RegisterHandler( "E2", Handler2 ); } </code></pre> <p><code>"E1"</code> and <code>"E2"</code> are names of tasks, that will have corresponding settings in scheduler config.</p> <p>Another approach is to use, for example, MEF. Each subsystem will export a set of <code>ISchedulerTask</code>s, and it will not register these tasks imperatively. And on the other side of application we will have <code>SchedulerTasksRegistry</code>, that will import a set of these <code>ISchedulerTask</code>s.</p> <p>In all approaches we will have a map in config, that will contain scheduling timeline for each task, identified in both approaches by its name.</p> <p>I am inclining to the second approach, but do not have enough arguments for it. Probably the only argument is that the first approach means higher static coupling of subsystems.</p> <p>Am I right, is the second approach better? What are arguments for any of these approaches?</p>
    singulars
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. PTQuestion
    1. USMikhail Brinchuk
    1. USMikhail Brinchuk
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. PO
      singulars
      1. PTAnswer
    1. VO
      singulars
      1. POScheduler tasks registration design
      1. This table or related slice is empty.
      1. VTUpMod
    2. VO
      singulars
      1. POScheduler tasks registration design
      1. This table or related slice is empty.
      1. VTUpMod
    1. COMy question is not about scheduler only. For example, similar question can be asked about some factories - we can this factory be built implicitly by means of MEF, that will search for all available implementations of interface that is returned by factory, and on the other hand we can create this factory imperatively with some kind of hard-coded switch.
      singulars
      1. POScheduler tasks registration design
      1. USMikhail Brinchuk
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload