Nicholas Lechnowskyj

My feedback

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

    Just want to point out that if you're writing enough unit tests you will find yourself only needing to deploy the cluster once for a final confirmation. All of the small during development prototyping is solved through unit/integration tests. Microservices make it very easy to obtain high test coverages.

  2. 1,103 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    28 comments  ·  Service Fabric  ·  Flag idea as inappropriate…  ·  Admin →
    Nicholas Lechnowskyj supported this idea  · 
  3. 224 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    under review  ·  7 comments  ·  Service Fabric  ·  Flag idea as inappropriate…  ·  Admin →
    Nicholas Lechnowskyj supported this idea  · 
    An error occurred while saving the comment
    Nicholas Lechnowskyj commented  · 

    We don't use one application > multiple services because this creates a dependency that microservices conceptually attempt to avoid. Each service is a completely independent unit, they have their own git repository, solution, build and release definitions. If you use one application and just want to deploy one service you'd have to share a common application manifest which I think is a big no no. So in other words we have 30 applications with 1 service inside each of them.

    As with most things, Microsoft is trying to support multiple use cases and fast time to delivery, however Service Fabric is an enterprise tool so I'm not sure why they are supporting "small mom and pop" use cases. If you're using Service Fabric and deploying to a Production environment from Visual Studio for instance that is absolutely ridiculous and honestly annoying that Microsoft actually spent the time to build out that type of tooling. It only serves to confuse people new to the platform and unsure of what best practices are.

Feedback and Knowledge Base