![]() ![]() Networking and security remains consistent regardless of how the app was built whether it be a microservice based app framework or a traditional waterfall model. The application is the focal point when it comes to NSX-T and it’s architecture. So when you think of NSX-T think “any endpoint, any site, any cloud.” Leveling the playing field from a network perspective, IT teams and development teams can now align the network with what suits their applications the best. Aside from meeting the demands in a vSphere environment it also addresses the needs for containers, bare metal deployments, 3rd party hypervisors and public clouds. NSX-T is designed with a lot of flexibility which enables it to meet the needs of various app frameworks, architectures, multiple endpoints and technology stacks. My main goal here is to increase your understanding of NSX-T and hopefully help you become more successful whether you’re preparing for a production deployment, have an upcoming POC where you need to be successful or simply looking to increase your knowledge of VMware NSX. TOR SWITCH TIER 1 FULLThis blog article is not intended to do a full side-by-side comparison between the two but I will point out some differences or similarities along the way. There are some differences between NSX-T and NSX-V that everyone should be aware of. Before I get into Part 2 of my Installing NSX-T mini blog series, let’s review some NSX-T components. ![]()
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |