Adding functional tests will be easier now that we have removed the Console App based calls from the service.
Performance testing will also be much easier as it'll be easier to concoct up benchmarking + scenario based perf testing.
2. Better extensibility such as changing the presentation
Envisioning different presentations can be built on top of the service such as that of a CSV file output or XAML based presentation.
By encapsulating the GCEnd logic into a simple Observable, we can start building more automated analysis tools (got a # of ideas here and will be happy to discuss via a PR).
We moved the core logic of the GCEnd event into it's own abstraction - the GCRealTimeMonService that's accessed via the IGCRealTimeMonService interface. The contract from the client of the service is to subscribe to the GCEndObservable to obtain the GCEnd events in realtime and call dispose on the IGCRealTimeMonResult once the program is to exit.
In an effort to separate out the core logic for:
1. Better testability
We moved the core logic of the
GCEnd
event into it's own abstraction - the GCRealTimeMonService that's accessed via theIGCRealTimeMonService
interface. The contract from the client of the service is to subscribe to the GCEndObservable to obtain the GCEnd events in realtime and call dispose on theIGCRealTimeMonResult
once the program is to exit.Usage:
When the process needs to exit: