Apigee Reviews

Essentially, we have our own product where we have hosted the APIs and Apigee for consumers to consume. We have an airline domain and our own product.

We provide services to our clients, who are end users.

We are experiencing issues with automation; the production in Apigee is quite time-consuming. 

The integration with serviceability also needs improvement. It gives our developers access. We have a developer who can deploy the APIs to the platform. As a result, they are encountering some difficulties in automating those processes. Stability relies on whether those issues can be addressed in any other API gateway.

I'd like to see the automation, time to release, time to market the new APIs, and pushing the APIs from one environment to another, to production, improved in the next release.

It is time-consuming; according to the information I have received, it can take up to two months for any new API to be published for production. I'm not sure what the difficulties are in between, but this is what I'm dealing with in this segment.

While I don't have the hands-on experience, in my opinion, and based on my research, it is not very user-friendly in terms of user experience, or UIUX.

I have been working with Apigee for a few years.

Apigee is quite stable.

The initial setup is complicated. There is a lot involved, and many teams are involved.

When attempting to apply a new host, they are setting up the DNS network, which takes some time.

We already have Apigee in our system, but we're trying to evaluate APM based on the differences between Apigee and APM.

Right now, I don't have any experience with Apigee. The only task I've been assigned is to evaluate the APIM. So far, I've only explored APIM. And all I'm doing is defining the features and differences between Apigee and APM.

I'm still evaluating, but in terms of overall performance and stability, it's quite good. As a result, we have not failed any of the issues in that regard.

For the technical capabilities, I would rate Apigee a seven out of ten.

We have a legacy and non-legacy databases that are both on-premises and off-premises.

Apigee is used to connect to any Google-based applications that are available. In addition, we are experimenting and testing in other environments.

I'm a CIO in consulting.

Apigee has proven to be one of the best of the breed. Others are attempting to innovate and are succeeding. So we don't know how innovations will be distributed, Azure, Amazon. Amazon, without a doubt, is lagging, but I've recently heard in the reinventing that they're working on a lot of API-related innovations. So you can't say that they'll be lagging behind as they are catching up.

We are experiencing some performance issues. Except in terms of performance, we can't find anything that needs improvement. This is something that we are trying to understand, and we will fix it soon.

I'm dealing with the Google and Apigee teams directly, so I can't go into specifics. But I believe we will be able to fix it sooner rather than later. It will be one of the most extensive implementations. And while we did not find any performance issues during testing and development, we did find some in production. We will be in a position to fix it soon.

Our environment consists of multiple clouds. The usual question is whether you have a single environment or a multi-cloud environment. What I've answered is applicable to all multi-cloud scenarios. I haven't specifically mentioned the Apigee-related issues. In CA Cloud, that is Google, I am working in a multi-cloud environment with settings and cross-components.

More platform integration, lower prices, and improved performance are all potential improvements; however, when it comes to standardization, all of them are converging on standardization, but, my criteria are more performance-based.

Either one is focusing on the API or on alternative exchanges that can improve performance. As a result, making a choice of API and the use cases that surround it, as well as how the implementation is done for scale, can be difficult at times. When we talk about the scale, there are definitely a lot of considerations that must be understood, and one of them is performance, which is our primary focus area.

If you are going to use APIs or even exchanges, you should be more concerned with performance.

I have been dealing with Apigee for quite a long time before it was part of Google. It's been approximately three years.

The stability of Apigee is one of the best of the breed.

The scalability of Apigee is good.

Apigee will be implemented in over 100 hospitals.

We have been working closely with technical support, and everything is fine.

We are also collaborating with Amazon teams and some of the standardization committees to help standardize APIs.

The integration of Apigee was straightforward.

It is not an installation, it's an integration. Apigee is integrated rather than installed.

The number of people needed to maintain this solution is determined by the project's, and the complexity of the situation.

Apigee is subject to licensing fees.

Typically, the customer is internal, so it is accounted for in the integrated budgets.

I have other affiliations. Like, I am associated with Cloud Security Alliance, which is a nonprofit organization. And I am also part of ISO SC 38. SC38 has a PWI, a preliminary work initiative on API management. And that goes as the advisory at a global level for a standardization. This topic is not only of my interest, but it is my passion.

I would recommend this solution based on the use case they have.

I would rate Apigee a nine out of ten.

One feature I found most valuable in Apigee is its simplicity. All features remain the same in all of the API tools, and I have experience with IBM API Connect and Apigee, but Apigee is easier to work with, plus the learning curve is not that steep.

Another thing I like about this solution is that the support is really good, and this gives Apigee advantage over other providers.

I like the development feature of Apigee. You will find it easier to work with Apigee than IBM API Connect.

We found a glitch in Apigee, and we raised it with them: It's the response overlapping from the API with high traffic.

They have been working on that, and they have shared a patch with us, but I'm not sure if that is publicly available for all users. It was made available to our organization: one single patch of Apigee.

I've been using Apigee for over two years, and I've used it in the last 12 months.

This product is is stable.

Apigee is a scalable product.

Technical support for Apigee is very good.

I used IBM API Connect, but found it easier to work with Apigee.

I evaluated IBM API Connect.

I'm both a user and an integrator of Apigee.

We have deployments both on-premises and via cloud. We use both, like Google SaaS and the on-premises solution.

We are a consultant for different organizations. Some organizations prefer on-premises deployment, with everything on their private cloud, and this means they use the older version of Apigee. Some organizations use the latest version because they're using Google SaaS directly.

My advice to people who are looking into implementing Apigee in their organization: If it fits your budget, then it is a good product. If it fits into your ecosystem, e.g. you are in that ecosystem, not in IBM or other CA-based ones, Apigee is something you can go for. It is a good platform.

I haven't worked with CA, and there are others, e.g. MuleSoft, so I can't comment on how Apigee compares with those competitors, but compared to IBM API Connect, Apigee is a good one.

I'm rating Apigee eight over ten. There's still room for improvement, so it's an eight for me.

One of our use cases for Apigee was when we were exposing a legacy application that we were using in the past.

As of now, we have not found anything major that needs improvement. It is not something that we are heavily using, it's something that is still in the process of being adopted company wide.

Maybe securing the APIs could be a little bit more straightforward. There might be some room for improvement in the process of securing the applications that we're exposing through the API. We would like additional documentation on this or some examples of how to do it. Overall, we have had to invest more time than expected to do that setup.

It would be good if the Apigee management allowed us to be able to consolidate many operations into a single one for the gateway functionality.

It has been two years that I am using Apigee.

It is stable.

It is scalable.

We have around four users.

There is a team of less than five people for deployment and maintenance.

As of now, we are going through a consolidation process within the company. Oliver Weyman is part of a larger group of companies. We are among the first ones to use it, but the plans for it are still not outlined for the next year, at least. This is something that we will finish figuring out within the next few quarters.

Support is good.

At the beginning the initial setup was very straightforward, but the fine tuning during the setup is something that needs some improvement. The initial setup was pretty straightforward because we were trying not to do very complicated things. The initial setup was easy. But then as we started to grow, we realized that there was some room for improvement, but overall the initial setup was easy and we liked that.

Since it initially started as a POC and then we started moving forward from there, it was not complicated. But had we started with a real life application or with more complex applications or requirements, it probably would have been more difficult for us. But the way that we decided to start and also because of the complexity level, it allowed us to go very smoothly with the first setup and deployment.

The implementation was all internal.

Normally the company tends to do agreements with the vendors, where we are trying to get everything in one single license so as not to add complexity to the licensing. That's what I recommend.

The company started evaluating solutions and we found that we have three other options. One of them was Mashery, the other one I don't remember the name, and the last one was SAP. The company decided to go for Apigee and now there are no plans to go to something else because the process that we take to evaluate and assess the solution is a very thorough process. We try to spend as much time as possible evaluating the pros and cons of the solutions and what issues might come up.

My advice to anyone considering Apigee is to start small and then grow from there. Try not to start migrating big, meaning to consolidate many applications into one single one. I would say to start small and try to run some POCs to make sure that they understand the fine tuning. Because the initial setup was easy but the one thing that needs time is the fine tuning of the setup. That, as I said before, is something that is really important for security. The security is something that I would recommend people look at.

On a scale of one to ten, I would give Apigee a nine out of 10.

If the budget is not a concern then I will choose to go with Apigee over WSA-2, but if it is then I would prefer the latter solution. Apigee is quite pricey. The price is a thorny issue as there is little room for negotiation. 

Unlike WSA, Apigee does not have a partnership model, something which makes it a bit easier for companies such as ours to go with the former solution. 

While I cannot comment definitively on the partnership issue, as the company has yet to get back to me, I can say that this issue and the one of the pricing are why I choose to rate the solution as a six out of ten. 

The stability is fine. 

Apigee has better scalability than WSA. 

While the technical support seems fine, I cannot comment on this with certainty, as we did not go ahead with implementation of the solution. Had we gone ahead with a partnership with Apigee, then I would be in a better position to do so. 

If the budget is not a concern then I will choose to go with Apigee over WSA-2, but if it is then I would prefer the latter solution. Apigee is quite pricey. The price is a thorny issue as there is little room for negotiations.

If the budget is not a concern then I will choose to go with Apigee over WSA-2, but if it is then I would prefer the latter solution. Apigee is quite pricey. The price is a thorny issue as there is little room for negotiations.

Unlike WSA, Apigee does not have a partnership model, something which makes it a bit easier for companies such as ours to go with the former solution.

Apigee has better scalability than WSA. 

We are customers of Apigee.

I rate Apigee as a six out of ten because of its pricing. 

Apigee is a platform for API management.

Apigee is a pioneer in the industry and has good features and functionalities. It is a good tool for API management and it has more advancements than all other tools in the market in certain areas.

It has many features, such as flexibility, coding writing, and JavaScripting.

I have been using Apigee for approximately four years.

Apigee is stable. In the entire API management world, I feel this is one of the best tools for pure API management. If there are any orchestrations or business processes to be involved, then Mulesoft or Boomi can be used, but comparatively, all the security and governance policies that are available on the dashboards and the reports make Apigee the best tool for pure API management.

The installation is good. I won't say it is complex, but it has many configurations and types of policies that are available. However, it can be easily done.

Apigee is slightly expensive, but again, it can depend on the type of usage. All things considered, it is slightly expensive. 

AWS is winning in the cost category, they have many packages and services but when using all these services together I am not sure what the cost would be.

I have evaluated Mulesoft and Boomi. I have found these two solutions are being used secondarily to Apigee. Additionally, AWS and Azure's Gateways are becoming popular in the market. From the cost perspective, in the two years, AWS gateway is widely being used. These four solutions are widely being used in the market but Apigee is much far ahead than all other tools.

AWS and Apigee have similar features. I don't see any significant change in the difference at the moment. The choice is more about convenience and cost.

I rate Apigee an eight out of ten.

I use it at home to scan my local drive for malware or viruses. 

I like Apigee's automatic plates.

Apigee's user interface could be more straightforward and have more options. Also, it would be nice if it were ready to work out of the box without so much configuration. Regarding features I'd like to see, they could add self-recovery from the last hour, the last day, etc.

I've used Apigee for around five years.

The stability and performance are both pretty good. However, I have an FFD disc, so I don't see the scans anymore. They're all done overnight.

The version I'm using isn't scalable. It's not the professional version. 

I have never called Apigee support. I haven't had any issues.

Installing Apigee is very simple and only takes two or three minutes.

The home version is completely free.

I rate Apigee seven out of 10. It's a good tool, but not a fantastic tool. I use it because it's simple, it automatically updates, and It hasn't given me any issues. 

I'm a part of a service provider company, and we basically provide all kinds of services for our customers. One of the areas for which we provide services is API management. We work a lot with Apigee, and we have experience and a good team working with Apigee.

In terms of use cases, we've created a good marketplace for one of the clients. They are a logistics company, and they have a lot of vendors and partners with whom they work. So, we have created a marketplace where the vendor's partners can integrate for their shipments and other things. They can integrate their applications into this marketplace.

We have also implemented developer portals where we do the onboarding of developers. They can create their code SDKs, etc.

Currently, we are at a customer site, and we are migrating the on-premise version H to Apigee X, which is the latest one.

The analytics function and the developer portal are the two valuable features of Apigee. The analytics part is very good, and the developer portal is quite rich in features.

The authentication mechanisms are quite easily built into Apigee, which is something that most of the other products have also now started supporting.

iPaaS is something that we would like to see. For example, MuleSoft is kind of an integrated platform as a service (iPaaS), and it provides a lot of out-of-the-box connectors and other such things. This is where Apigee lacks. I'm not sure if that's the roadmap for Apigee, but any improvements on those lines would be helpful where things become easier to implement.

It has been four to five years.

It is definitely stable. Performance-wise, we have not seen any major bottlenecks. What we have realized is that the performance is not just because of the tool itself. If you take any API management tool, the performance also depends on the way the integrations are done. So, if implemented correctly, performance is not really an issue.

With the SaaS model, scalability is there. 

It is suitable for large companies because it is a bit pricey. It is definitely not for small companies, but it might be suitable for medium companies.

We have not been in touch with them much because we mostly have done development, but they do provide good support. Their support during the initial design architecture phase is also very good. So, if you have bought the licenses, they do provide an architect to come in and define the whole architecture. That way, the support is good.

We work on multiple API management tools based on the requirement of a particular customer. We have worked on Apigee, Dotcom, MuleSoft, to name a few.

Managing an on-premise setup themselves can be a huge overhead for customers. Apigee, I believe, releases patches very frequently, and those upgrades and maintenance activities are quite an overhead. Having said that, it has good support. They provide a lot of scripts through which the installation and other things can be automated, but obviously, we have to tailor those to our needs. On-premise is definitely a little bit of overhead. We have to have a team to manage that, but now with Apigee X going on SaaS, most of the implementations are on SaaS. So, this overhead is minimized a lot, and you just have to do the configurations.

It is a bit on the expensive side. Its licensing cost is a bit high, and that's where we've seen people going back on their decisions.

In the latest version of Apigee, they've broadened the support for socket communication, which was previously missing in Apigee Hybrid.

I wouldn't recommend Apigee for simple situations because sometimes, it does become an overhead. It is overkill for simple situations. If you have very complex scenarios where you are trying to embark on a cloud journey and you still have systems on-premise or some systems are hosted on some other cloud and you want to do an integration, Apigee is really good. It provides support for the mesh architecture, and with that, it becomes quite easy.

The advice that we normally give is that when you are starting on an Apigee journey, you should not think of it just as an API management tool. We try to give it as an enterprise API platform that a large customer with different lines and businesses, such as a bank, would eventually leverage as a whole. You should not treat it in a way where only a particular group is using Apigee. It is an enterprise platform. So, you should treat it as a platform.

I would rate Apigee an eight out of 10.