Osita Chris Okonkwo

My feedback

  1. 996 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    26 comments  ·  Service Fabric  ·  Flag idea as inappropriate…  ·  Admin →
    An error occurred while saving the comment
    Osita Chris Okonkwo commented  · 

    My scenario:
    Need to migrate mulitple Windows/ServiceHost services with complex async logic to SF as stateful services. The services are shutdown during weekends by a managed shutdown of the server. Server is restarted early Monday morning.

    From a deep dive into Actors, something similar may be possible: Actors are garbage collected if they do not receive a method invocation after a configurable period of time. The rub is that Actors are single-threaded. I can rewrite my multiple async services as amalgams of single-threaded Actor workloads that are orchestrated by a single 'master' async stateful service. Thus, over the weekend, my services (minus the 'master' service) will be stopped since no Actors will be active.

    But that will be one helluva re-write. :-(

    Would be a much happier camper if a configurable stop/disable of the stateful and stateless services were possible.

    /oco

Feedback and Knowledge Base