Francesc Castells

My feedback

  1. 74 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    6 comments  ·  Service Fabric  ·  Flag idea as inappropriate…  ·  Admin →
    Francesc Castells supported this idea  · 
  2. 954 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    25 comments  ·  Service Fabric  ·  Flag idea as inappropriate…  ·  Admin →
    Francesc Castells commented  · 

    Another scenario: a service processes messages from a queue and you want to stop it. You might want this for several reasons:
    1.- The service has a bug and all messages fail. Let the messages pile on the queue, fix the bug and redeploy
    2.- The service relies on an external service that is down (similar than 1)
    3.- You want to run the service locally for debugging, but the service in the cluster is taking the messages from the queue faster. Stop the service so your local instance can pick the messages.

  3. 1,059 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    under review  ·  16 comments  ·  Service Fabric  ·  Flag idea as inappropriate…  ·  Admin →
    Francesc Castells commented  · 

    I don't understand this requirement. Why not use one of the many existing messaging technologies? Azure Service Bus for example. If you need a higher level abstraction of the messaging technology you can use an existing framework like MassTransit or NServiceBus.

Feedback and Knowledge Base