The standard deployment is very simple.

The initial setup is very easy to install. Deployment hardly takes 15 minutes. You don't need customization. Everything is pre-configured for you. Just click to deploy and start your development.

The initial setup is easy.

Deploying 3scale is straightforward. It is deployed on an OpenShift Container Platform. You create an instance, configure 3scale, and run the OpenShift container. 

Not complex, the cloud integration is even the quickest one based on containers.

The deployment process is not that complex, but we have had issues with operators that have been hard to configure with our GitOps strategy. We want to deploy everything based on Argo CD with GitOps, and it hasn't been possible to do that with the operator part of the gateway. We've run into a few issues there.

We did the deployment in another part of the organization at first, and now we have done it in our target environments, with our target vendors. I wasn't involved in the first round, with version 2.5, but I have been involved in deploying the later version.

The time it took for deployment doesn't have as much to do with Red Hat as it has to do with our setup with GitOps and our vendors. The installation process is quite fast, but figuring out the issue with the operators and why that is not working has cost us quite a lot of time. But overall, the installation part is quite smooth.

We have one gateway for customer-facing, external APIs, proxying all the traffic from the customers, partners, external parties. And after some consideration and talking back and forth with Red Hat, we decided to have an internal gateway for internal APIs and that one is available for all internal applications. Internal applications are internal to the organization, but they don't have to be in the same network. They could be on an external network. And we may not have made the right decision there. We had a bit of a problem understanding why we should have internal APIs. Because we are going with API-first, we believe that we should externalize all APIs.

I would say the initial setup is straightforward. I haven't been doing the installation by myself. The operation people have done that, but it went well and we had no problem with that.

They said it should take just an hour or two, and we were laughing. That's what it should've taken, but I would say that they were done in a week. I think when you come to a new environment, it's not just the product. It's other things as well. So I would say that one week is pretty efficient.

The initial setup is complex at the beginning because there are a lot of steps that we have to follow. Two to three people are needed for deployment and maintenance, at least.

It takes approximately six months to deploy.