Cisco Application Centric Infrastructure (ACI) is network virtualization technology.
N/A
NGINX
Score 9.1 out of 10
Mid-Size Companies (51-1,000 employees)
NGINX, a business unit of F5 Networks, powers over 65% of the world's busiest websites and web applications. NGINX started out as an open source web server and reverse proxy, built to be faster and more efficient than Apache. Over the years, NGINX has built a suite of infrastructure software products o tackle some of the biggest challenges in managing high-transaction applications. NGINX offers a suite of products to form the core of what organizations need to create…
N/A
VMware NSX
Score 8.8 out of 10
N/A
VMware NSX is network virtualization technology. VMware NSX is no longer sold as a standalone product and is now available as a part of VMware Cloud Foundation.
An alternative to ACI would be to use VMware NSX-T. The advantage of NSX-T is that the micro-segmentation is implemented with a distributed firewall and not with ACL. The disadvantages are that you would still need an additional pyhsical network as underlay that has to be …
The main reason we decided to go with Cisco ACI over VMware NSX was that with ACI we could still connect physical networks, therefore, utilizing ACI as our complete data center switching platform. NSX was really only a solution for virtualized networks.
It’s native support to applications through Application centric mode it’s attractive when deploying in a private cloud environment and it’s ease integration to compute/VMM resources allows the deployment procedure to be much efficient. Also Cisco is a lead in the market that …
NSX-T and ACI both are definitely awesome products. I tend to use ACI in networks that have more barebone and/or alternative hypervisors. NSX still works best in VMware heavy networks. Another consideration is where the network is managed, by which team. If the network is …
Enable full automation of physical and virtual network. Legacy network devices can be physically connected to the fabric. Hardware routing is much more efficient than a software only network.
Cisco is Cisco. You have the ecosystem and you have end-to-end technology line-up and the integrations against the rest of the portfolio. No other vender has broad view.
We use both Cisco ACI and VMware NSX, and while they have different strengths and capabilities, I would recommend VMware NSX, as it can be used in all VMware environments, without costly physical infrastructure changes. Cisco ACI provides some of the same capabilities, but not …
We use both ACI & NSX. They both provide a programmable network and in future releases of ACI they will allow you to stretch fabrics into the cloud like you can do with NSX. ACI, when compared to NSX, turned out to be significantly cheaper, but it also was lacking certain …
The ACI solution is perfectly fit for a large or multi-site data center environment. It permits simplifying deployment, management, automation, and security. ACI is especially valuable when strong scalability, automation, security, and segmentation are required. However, ACI is less suitable for a small environment due to its complexity and high cost.
Nginx is well-suited for any web server scenarios, such as web applications, backend or reverse proxy for both application and HTTP requests, and distribution. It is less appropriate for Windows-based applications that run directly on a Windows Server host. In any case, it is very easy to manage, through separate conf files for each application or site you want to host with it.
With proper design, VMware NSX can and should be deployed to virtually any VMware virtualization environment, but the deployment should be tailored to the needs of that environment. There isn't really a one size fits all deployment design for all environments. That versatility is what provides its greatest strength to a business.
Cisco ACI, The object model is very complicated. It's something difficult to understand and also because there is a user interface, there's a web user interface, but it's not optimal to use it because if you want to deploy a large amount of VLAN or a large amount of tenants, it's quite difficult to do it or it's quite challenging. Maybe if you want to configure a large amount of ports using the web interface, it's not appropriate because it takes a lot of time. It also provides APIs to do that, but as I say, the object model is very difficult to understand and there is very little documentation about automation of the ACI and maybe there is but it's not so easy to find.
I think something I've just went to a session with hyper fabric and the ideas that hyper fabric has. Keep it really simple because Cisco ACI is a complex system and adopt some of the ideas behind hyper fabric, bring it to ACI that will be really beneficial. So as I said, automation is a great thing, but it's still, you need to have the background and the really complex stuff that happens behind the scenes to leverage the value of that solution. And by adding more simplicity to it, I think that will be a great thing. And also integrating with other applications in terms of the automation.
Customer support can be strangely condescending, perhaps it's a language issue?
I find it a little weird how the release versions used for Nginx+ aren't the same as for open source version. It can be very confusing to determine the cross-compatibility of modules, etc., because of this.
It seems like some (most?) modules on their own site are ancient and no longer supported, so their documentation in this area needs work.
It's difficult to navigate between nginx.com commercial site and customer support. They need to be integrated together.
I'd love to see more work done on nginx+ monitoring without requiring logging every request. I understand that many statistics can only be derived from logs, but plenty should work without that. Logging is not an option in many environments.
Provided with the intensive fault isolation for the CISCO ACI, we are glad that we have this Data Center Solution in place and we will continue to renew as long as the future needed requirements are meet and more helpful features will be enabled in the future with the integration of security
You'll need a lot of training and hands on experience to get the most out of the product. There are a lot of very useful features in the ACI product. Often times there are a lot of ways to get to a solution for chalanges in the field. The solutions might be different eacht time. Knowing which one to implement is somtimes a challenge.
This tool is really easy to use and configure. Consumes very less system resources. It is highly modular and configurable. You can easily use it with other tools like certbot for SSLs. You can configure basic security with configuration and headers
It allways works. If there are problems with links going down by accident (say someone accidentally unpatches something they shouldn't have), we rarely miss more then one packet over the link. Also, using VPCs we are able to upgrade the software on the switches without the attached EPs ever noticing.
Day to day operations on Cisco ACI do not require much human intervention, the platform ticks over without any major faults. Being able to rapidly replicate the communication between two groups of machines across multiple sub networks speeds up new application delivery, and the integration into vmWare allows multiple teams within IT to work together to problem solve rapidly.
Cisco provides users and partners with a multitude of data for you to consume. I think that the stuff in the public domain goes a long way to assisting you find any answers you may need, plus insights and information from areas such as DevNet provide you with access to more than just the traditional release notes and the like
Community support is great, and they've also had a presence at conferences. Overall, there is no shortage of documentation and community support. We're currently using it to serve up some WordPress sites, and configuring NGINX for this purpose is well documented.
The Cisco ACI training provided by Cisco was in depth, covered all of our requirements, and allowed us to implement and maintain the platform without issues.
Being involved in the implmentation gives you more overview on how things are supposed to be working and communicating, you can easily performce troubleshooting and understanding the troubleshooting scenario
Actually we start our learning in networking career with Cisco. So it is very useful or easier to learn this product. And honestly speaking, I didn't work in any other data center solution other than Cisco. So I cannot compare what it gives us more than other popular stuff. But this is very nice product like from Cisco.
I have found that [NGINX] seems to perform better throughout the years with less issues although I've used Apache more. I would definitely recommend [NGINX] for any high volume site and I've seen this to usually be the case from most provided web hosts who will pick [NGINX] over alternatives
We use both Cisco ACI and VMware NSX, and while they have different strengths and capabilities, I would recommend VMware NSX, as it can be used in all VMware environments, without costly physical infrastructure changes. Cisco ACI provides some of the same capabilities, but not all. It's focus relies on physical networking changes.
Cisco ACI scales well and is suited in scenarios such as multi-cloud or large data centre implementations. It is not suited to smaller deployments as the efficiencies that it provides are not fully realised. It is well suited in large environments that contain both virtual and bare-metal machines allowing a great deal of flexibility. It is also perfect to support multi-tenancy platforms.
We've definitely spent quite a bit of time relearning how to do things in ACI, but I think the investment has been well worth while considering that we can now deploy tenants and leaves from the ground up in a matter of seconds.
We can if we choose to upgrade an entire datacenters worth of switches in a single night. (We've chosen to break it up for availability requirements, but if you didn't require 99.999% uptime like us you may be able to do it)
By using Nginx, we can host multiple web services on a single server, keeping our infrastructure costs lower.
Nginx maintains our HTTPS connections, allowing us to keep our promise to our customers that their data is safe in transit.
Due to Nginx's extremely low failure rate, our web addresses always return something meaningful, even when individual services go down. In sense, this means we are "always online" and allows us to maintain brand and support our customers even in the face of catastrophe.
