IBM API Connect was already an existing middleware for the client, and we only expanded it for our new digital transformation project. So, the deployment process wasn't relevant to my experience.

Only two people manage it. They handle the entire API lifecycle, including hosting and management, across four different environments. They're DevOps engineers, playing both development and operations management roles.

The initial installation phase may pose challenges as it requires some time to grasp the intricacies. The learning curve is significant, especially for people who don't have experience with it. While the installation may not be easy initially, users can acquire proficiency once they have a thorough understanding of the system. When deploying a new environment, the entire setup typically takes approximately one to two days. Assigning two individuals to manage the deployment process is more than sufficient. For ongoing maintenance of the solution, a single person is capable of handling all the necessary tasks efficiently.

The solution is deployed by our in-house team.

I've implemented this solution through a vendor team. I've always used consultants, partners, or integrators for implementing products.

The deployment process is facilitated and fast. It takes about an hour for the solution to be deployed.

We use a team from IBM that assisted us with the implementation.

The solution was first set up with the help of IBM, but when we moved to another environment, we followed the initial instructions given by IBM and implemented it ourselves. 

We used Bamboo as a pipeline for automatic deployment of the API. The deployment took four hours.

I did the implementation myself.

We provide this solution to customers. 

We used IBM directly for implementation. We've been using IBM services for the past 13 years, and we are okay with their level of expertise.

We have an architectural roadmap to follow while doing the implementation of the solution and it took approximately three months for our teams to complete. I had some support from IBM during the process.

We implemented it with the official vendor of the product.

We used IBM directly because we bought the product from them. We basically got them onsite to explain what their blueprint meant. The documentation was quite good, so all we had to do is get them to come and agree with the pattern we've selected. Now we're still finding our feet, experimenting and making up our minds.

We worked with a certified external consultant company.

We used a local broker to assist in the implementation.

Initial set up was done by IBM but new VMs are configured by us.

We did it in house using the same set of Datapower developers supported API Management.

One member of our team implements this solution.

During the setup, we had to get some professional help from IBM itself. We have people that got trained on the solution, and in terms of integration, they got trained on it. And so they will have knowledge on how to create new integrations and new APIs on it and how to expose APIs on it going forward.

The implementation team did it with the support of a main vendor team. They have high level of expertise.

We outsource maintenance to a local company in Finland. They built it for us and maintain it.

It takes one person to set up, max two, as it is straightforward. There is not a lot to do. The system admin will probably spend one to two hours on it to maintain it.

It takes us a week or two to set up 50 services in API Connect. The only thing that might take extra time is portal design because that requires us to go into the back-end.

We implemented through an in-house team. 

We were working with IBM for the implementation.