Basic deployment can be done in 60 to 90 minutes.

If you're going into automation, you need one or two engineers maximum who will do the deployment and installation. If the user is self-sufficient and in DevOps, then you don't need anybody else.

The tool is pretty easy to deploy.

The initial setup is not difficult. You need to have some experience, of course. When installing the solution, you just edit some text files. It could be simpler if you have a user interface, but you must know how to edit a text file.

Setting up NGINX Plus is generally straightforward and not very complex. While some modules may not be included in the documentation, finding and installing them is manageable. The deployment process is relatively simple and can be started right away, especially if you have prior knowledge of NGINX. 

For deploying and maintaining NGINX Plus, the team size varies based on the environment's scale. In a large setup, we might need four to five people, while in smaller environments, two technically sound individuals can handle it.

Setup is very easy. It's easier to set up than Apache. There's a lot of documentation on the internet.

If someone is knowledgeable, they can implement the solution in 30 minutes. It depends on the infrastructure and the services in the company.

It's not a complicated solution. One or two people can implement it.

The initial setup is very easy. 

The initial setup is not simple. We have three people working on the solution.

The initial setup was not complex. It was easy. It took us one or two days to set it up.

The solution’s implementation is very straightforward. The deployment takes around two to three days to complete. However, the solution’s implementation will depend from organization to organization. Some of the packages can be blocked by their BLP. If a company has full internet access, one to two days would be enough to do the POC. In fact, one hour would be enough if the company has full internet access.

We use CLI-based installation process in docker. If you use docker filing for the solution, then the installation is too easy. You can build a server within two to three minutes if you have the image of the application.

NGINX is a little complex to implement and requires a certain level of knowledge including at the application level when different websites need to be redirected.  Using the redirection requires some knowledge about the application aspect and that's somewhat complicated. Deployment was carried out in-house. We're currently using 10 nodes and we won't be expanding in the near future. 

I don’t have any insights as far as the setup goes. I came to the company after it was deployed.

However, my understanding is that it wouldn’t be complicated as everything is automated.

For maintenance, we have two people managing the solution.

The initial setup of NGINX Plus is very simple to deploy since it is done on a cloud.

The solution is deployed on the cloud.

The architecture is slightly different from F5 because it is based on VMs. F5 has an appliance, but it's a legacy style, whereas NGINX has both the VM and the appliance. The controller, which controls and pushes configuration, and the orchestrator are both parts of the VM. It is not difficult; it is simply different.

The initial setup is straightforward.

The initial setup is straightforward. It took about a week to deploy the solution.

This was installed on an Ubuntu system. The setup and deployment is well documented which lead to creating an easy hosting environment.

NGINX initial configuration is straightforward.

NGINX Plus is simple to deploy even during advanced implementation.

Get a real good engineer who will do this for your business. I did, and I am happy with it.

The initial setup is straightforward for those who are used to reverse proxies and/or load balancer terminology. The NGINX default install sets up an example web server, modifying it from there is very straightforward, and their documentation is fairly good. 

The initial setup can be complex. You really have to have a good understanding of their configurations. On a scale from one to five, I consider it a three.

I think installation only took a couple of minutes — no more than 10 minutes.

It was a simple setup.

Complex. It needed a complete product rework.