Sunday, December 6, 2020

Network Engineering continued ...

   This is a continuation of the earlier posts starting with this one: http://ravinote.blogspot.com/2020/09/best-practice-from-networking.html

  1. There are notions of SaaS, PaaS and, IaaS with clear separation of concerns in the cloud. The same applies to any solution deployed to these. 


  1. The organization of services in the cloud does not limit the number and type of solutions hosted in the cloud. The same holds true for the feature as services within a multi-tenant hybrid cloud with proper isolation. 


  1. The benefits that come with the cloud can also come from a networking layer and software defined stack. If an application uses cloud only to aggregate traffic, it could consider moving to on-premise with a fully managed networking layer.

  2.  

  1. There are times when the networking layer will have imbalanced load. They will need to be load balanced. Since this is an ongoing activity, it can be periodically scheduled or responded when thresholds are crossed. A load balancer does that automatically.


  1. When the layers of infrastructure and networking services are clearly differentiated, the upper layer may utilize the alerting from the lower layers for health checks and to take corrective actions.

  2.  

  1. There are several ways to monitor networking whether it is for performance, statistics or health checks. A system center management system can consolidate and unify the operations management. The networking layer  merely needs to publish to a system center. 

No comments:

Post a Comment