When you start Service Fabric Explorer, the following window will appear:
Note that the tree view to the left displays Application View and Node View:
The pane on the right-hand side will display information regarding the local cluster. This makes it easy for you to see the overall health of the local Service Cluster:
When you expand Application View, you will notice that our sfApp service has been published. Expanding it even further, you will see that the sfApp service has been published on Node_3. Expand Node View and Node_3 to see the service active on that node:
To illustrate the scalability of microservices, right-click on Node_3, and from the context menu select Activate / Deactivate and Deactivate (remove data) on the node. Then, click on the Refresh button at the top of the window to refresh the nodes and applications.
If you now go ahead and expand Application View and look at the service again, you will notice that the Service Fabric cluster noticed that Node_3 was disabled. It then automatically pushed the service onto a new, healthy node (in this case, Node_2):
The local cluster nodes view in the right panel of Service Fabric Explorer also reports that Node_3 is disabled. Click on Node View to see this:
