Anonymous

My feedback

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

    This would be pretty cool. It means I wouldn't have to make a facade layer for every endpoint.

  2. 153 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    11 comments  ·  Service Fabric  ·  Flag idea as inappropriate…  ·  Admin →
    Anonymous supported this idea  · 
    An error occurred while saving the comment
    Anonymous commented  · 

    Having to place every actor on every node is the main reason we haven't started using Azure Service Fabric. It's the biggest anti-pattern and almost makes the entire architecture useless for some applications which would normally greatly benefit from the distributed system.

  3. 388 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    under review  ·  2 comments  ·  Service Fabric  ·  Flag idea as inappropriate…  ·  Admin →
    Anonymous supported this idea  · 
  4. 1,408 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    85 comments  ·  Storage » Tables  ·  Flag idea as inappropriate…  ·  Admin →
    An error occurred while saving the comment
    Anonymous commented  · 

    While I agree that built-in secondary indexes would be nice, in most cases it's better to consider indexes on a case-by-case basis and implement the index differently depending on your queries and their frequency. Information on creating your own secondary indexes can be found here https://msdn.microsoft.com/en-us/library/dn589791.aspx

    Anonymous supported this idea  · 

Feedback and Knowledge Base