It depends on features/budget etc... in addiction of a centralized management, dvs gains these features:
- inbound traffic shaping
- vswitch port mirroring/blocking
- load based teaming
It depends on your purpose... If you are a cloud provider I suggest the use of a dvs instead a vss (if you want to use nsx this feature is mandatory)...If the purpose of your vDC is a simple "little infrastructure" where license cost is critical, I suggest the use of a vss (with some powercli scripts for a day by day operations)
Thanks for reply, I want to understand from design best practices, I have a license however, I do not want to use any extra capabilities of dvswitch as I am not even using it in standard switch. What vmware recommends in such scenarios? If i look at administration part, I think vswitch is easy to manage as compare to dvswitch.
Also don't you think that with less no of host dvswitch can become an issue?
Desing best practices are simply guidelines, and the case of virtual networking, they are trying to establish a minimum watermark to achieve your objective... from license perspective if your license includes this feature: why don't use it? but from management perspective if you have trouble to manage dvs instead vss why choose dvs? (this is a more practical approach)
In design scenario vmware suggests the use of qualificators (Availability, Recoverability, Manageability, Cost, Performance, Security) to justify the use of vss or dvs... The workload critical analisys bring this the decision.
IMHO, 3 or more host with vcenter but standard or ent license implies the use of a vss. less than 3 (of course 2 simple esxi hosts without vcenter) use vss... 3 or more host with ent+ or vCAN program (VSPP) I suggest the use of dvs, because is easier to manage and scale out. But if you fear about the use of vss, I suggest to learn more about dvs... but if you feel comfortable to use vss, feel free to use it.