Note that there are some explanatory texts on larger screens.

plurals
  1. POHow to implement Monitoring the right way in a SOA DDD Environment?
    primarykey
    data
    text
    <p>We try to follow SOA and DDD principles in our project. We use NServicebus as messaging bus. So far we have 20+ services.</p> <p>How do you guys set up monitoring (i'm not talking about technical monitoring - like is service "xyz" reachable - is the hard disk full) ?</p> <p><strong>For example</strong></p> <p>If an Order is placed and the shipping is done 5 days later but it should have been executed after 1 day ... that's an error condition.</p> <p>Or another example: The shipping is done. Now we send an electronic invoice to our customer. We must archive that invoice and talk asynchronously with a third party (archiving provider) to retrieve our invoice. If that invoice is not retrieved after 5 days ... that's an error condition.</p> <p>I have problems when defining HOW to model criterias on what is an error and WHERE to put these criterias.</p> <p><strong>WHERE ...</strong></p> <p>... do you set up Monitoring rules ?</p> <p>Are monitoring rules part of your bounded context ? I think yes.<br> Are monitoring rules directly related to an entity ? I think no.<br> Are monitoring rules directly related to an aggregate ? I think no. </p> <p>Monitoring rules are like Domain-Services that span multiple aggregates but as opposed to domain services can also span multiple bounded contexts.</p> <p>Who is reponsible ?</p> <p><strong>HOW ...</strong></p> <p>... do you set up Monitoring rules in code ?</p> <p>If you want to do it right its a really great deal of effort. Otherwise you could do it really cheap (make some queries here and there) but thats against SOA (the major part i'm concerned about)</p> <p>Please guide me to a clear and easy to implement solution.</p> <p>I'm also really excited to learn how you set this up.</p>
    singulars
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    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.
 

Querying!

 
Guidance

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