What advice do you have for others considering Apigee?

I would rate it a nine out of ten.

I rate the overall product a ten out of ten.

We are a service provider. Our customers use Apigee. We are also partners with Google. We are SI integrators. The tool is quite stable. It has rich features. Customers prefer it if they can afford it. It is one of the best products we have. Overall, I rate the product a seven or eight out of ten.

Overall, I would rate it seven out of ten.

Apigee is deployed on the cloud in our organization. I would recommend the solution to other users. Our clients for Apigee are mostly medium and enterprise businesses. Overall, I rate Apigee a nine out of ten.

Apigee is used by one of the largest healthcare groups, which has over 50 hospitals, and each hospital has 50 to 60 applications. I would recommend Apigee to other users. Overall, I rate Apigee a nine out of ten.

If you have numerous applications and high traffic, Apigee is a strong choice for its excellent features and outstanding performance. However, if your requirements are minimal and you don't need many features, there are other competitive API management products available. These alternatives can be more cost-effective. If you're looking for an open-source option and don't have critical applications that necessitate specific features, then Apigee is a suitable choice. I would overall rate it an eight out of ten.

The solution is advanced. It works efficiently compared to other solutions, such as MuleSoft. I highly recommend it out of all the integration platforms. I rate it as an eight.

We are using the latest version of the solution. We're new to the product. I'm not sure which deployment we are using. I'm a customer and end-user. I'd recommend it to others. So far, using it has been very helpful. I'd rate the solution eight out of ten.

We currently have only one customer with Apigee. I would rate this solution as a whole an eight, on a scale from one to 10, with one being the worst and 10 being the best.

I am using the latest version of the solution. I'm not sure if I would recommend the solution to others. I still need to make comparisons between this and other options. I'm trying to decide if I should stick with Apigee or move to something else. So far, I'd rate the solution eight out of ten. It has a high rating on Gartner.

I used Apigee for my customer, but I no longer work for the company. I'm a content writer and was involved in researching and creating documentation about Apigee for a client. The majority of the clients had fifteen to twenty users of Apigee. My rating for Apigee is seven out of ten. The company was an Apigee partner.

When comparing this solution to others, such as Axway AMPLIFY API Management Layer7 API Management, Apigee is a more stable and mature solution. Being a SaaS platform, you do not need to worry about deployment, scalability, server performance, and other related issues. However, with the upcoming release of Apigee X, there may be some constraints applied to the current version. If you choose to continue using Apigee it is a good choice. I rate Apigee a nine out of ten.

I would rate this solution as eight out of ten. I would recommend this solution to those who want to start using it, but it depends on the requirements and automation.

If customers are trying to do long-term planning, and want to apply monetization on their APIs, then Apigee will be the best in this situation. I would rate Apigee a nine out of ten.

I rate the solution a seven out of ten. The solution is good, but the account simplification process can be improved. I advise users considering this solution to go for it because it has many API management features, including the health log error-finding tool and developing a new proxy.

I'd recommend the solution to others. It is costly but good. I'd rate the solution eight out of ten.

I would rate Apigee a nine out of ten.

Apigee has so many servers nowadays that are based on requirements. Much of the information is available on Apigee documentation which is good. I rate this solution eight out of 10.

I'm just a customer. It's a hosted solution. It's my understanding that it gets updated by Google when it needs to be. I'd advise potential users to do as many POCs as they can on the free version, and get their feet wet with it. There's a lot they can do with the free version. You can learn a lot by just getting out there and starting. I would rate the solution eight out of ten.

We're a customer and an end-user. I'd advise potential new users to understand if there is a fit as a product like this is pretty much covering the same functionalities as others on the market. There are not so many huge differences. It depends on what you have to do and what your capabilities are and what your vision is. If you need more freedom, you can use other things like Kong or other products. Usually, all those products, at least the big players on the market, have the same functionalities. At that point, it's just a matter of questioning if the product is fitting the needs and the purpose that the company has or not. New users need to question what they want to achieve and how they want to achieve it, how they're structured if they're working on the cloud or if they're working on-premise. They have to make some questions about the needs, the wishes, and the setup that they want to have. I'd rate the solution an eight out of ten.

I would recommend this solution to potential users. On a scale from one to ten, I would give Apigee a nine.

I would rate it a nine out of ten.

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.

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.

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.

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

I would recommend this solution to others, it is a good choice. I rate Apigee a nine out of ten.

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.

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.

I rate Apigee an eight out of ten.

I recommend this solution. Apigee offers a month free usage so you can play around and explore the product and then make a decision. We had a good opportunity to test things out before purchasing the solution. I rate this solution an eight out of 10.

Because of the multiple components it has, if you are trying to implement this in your environment, you need people who are experienced in most of these open-source utilities, such as NGINX, Drupal, OpenAL, etc. You would require someone knowledgeable in those utilities to be able to support the environment. I would rate Apigee an eight out of ten.

We don't directly use the solution we are a service company so we help our customers use the product. We are consultants. I can't say which version of the solution we're using at this time. I'd advise other organizations that you have value any solution beyond a price comparison with other API management solutions. You will need to look at APS strategies needed in the organization and the importance of creating API products. Once that strategy is laid out you can put the right resources in place. Basically, everyone needs to have a plan first before investing in an API management solution. In terms of Apigee, more exposure of the platform to wider stakeholders will definitely help in modeling best practice principles into EPA communication and evolution. I would rate the product at a nine out of ten. There's always room for improvement. However, it's not heavily technical. There's a lot of flexibility for developers to bring in customization. It's not rigid. If you have a team looking at APS cases, products, and you, how a corresponding APA team strategy, Apigee as a platform is very good. It's quite a comprehensive option.

We are systems integrators. We aren't just end-users. In general, I would rate this solution at an eight out of ten. If the pricing in relation to scaling was better, or if they offered better partner training, I would rate them higher. There aren't really any features lacking and we're largely happy with the product.

I would recommend this solution to others who are interested in using it. It's a very good product. I would rate Apigee a ten out of ten.

If your workload is already deployed on Google Cloud, integration is very easy. Even if your services are hosted in some other cloud, like AWS, I think you can use Apigee, but I haven't tried that approach. On a scale from one to ten, I would give Apigee a seven.

I would rate this solution an eight out of ten.

For potential users of Apigee, I'd tell them there's a free version if they want to check it out and have a trial. On a scale from one to ten, I would give Apigee an eight.

We're just a customer. We don't have a business relationship with Google. Overall, I would rate the solution nine out of ten. Whether of not this is a good solution for a company depends on a lot of criteria. The budget itself needs to be considered, for example. Apigee is perfect. They provide good support. People from Google are very cooperative as well. They listen for feedback on features. They don't provide a partnership to just any company. You need strong criteria to get a partnership and to be able to support and feature the license. I like this, to be honest with you. That's already making our implementation easy. We're only dealing with companies that know how to do work in Apigee setup and installation and configuration and they have a long history of providing strong criteria. In general, I recommend Apigee.

I would definitely recommend this solution. It is a good solution for masking data, using methods like RPC, and administering APIs. We plan to continue using this solution. We have legacy systems in our company, and we need to move to new technologies. We plan to create developer APIs for the rest of the functionality and use Apigee for API management in our company. I would rate Apigee a nine out of ten. It is an excellent product.

I would go with Apigee if you have the money. It will give you enough APIs for management. If you're looking simply for one functionality then I wouldn't recommend Apigee. I would rate this solution an eight out of 10.

We're just a customer. We don't have a business relationship with the company. We are removing our IBM products and transition completely over to Apigee. We have Azure's API as well. In next one year or two year, we are going to dissolve IBM API Connect as well as Azure CIM and move everything to Apigee. Overall, on a scale from one to ten, I'd rate Apigee at an eight. We'd rate it higher, however, they aren't clear on their offering. We just want everything automated and easy. The cost is not the issue. The lack of information is. I'd recommend the solution. It's a nice product and companies should go ahead with it, so long as they are okay with the pricing, as it is rather expensive. If a company is cost-consious, IBM API Connect may be better as the licensing costs are lower.

I would definitely recommend this product over any other products available in the market in this category. It has all the features necessary to work in anything from a basic scenario to advanced applications. So I find that everything in it is flexible and available in this one product. Because of that I highly recommend it to anyone. On a scale of one to ten (where one is the worst and ten is the best), I would rate Apigee around an eight out-of-ten.

What I would recommend for clients who are considering this type of solution depends on the customer's use cases. Since we are Google partners we generally go with Apigee as the solution. But if the client insists that there has to be a lot of orchestration and other integrations need to be done, then we will go with MuleSoft. On a scale from one to ten where one is the worst and ten is the best, I would rate Apigee as somewhere around an eight.

My advice for anybody who is considering Apigee is to first do research and an analysis of what they want to use it for, including specific use cases. It is a good tool but it is important to have well-defined requirements to avoid a high implementation cost and rework. The requirements have to be very well documented and understood by all parties, especially those who will be involved in implementing it. Following this approach is an important step to getting a good return on investment. I would rate this solution an eight out of ten.

This is a very good API tool. I think that this solution is very good in some use cases but not very good for some small companies. It can be complicated for licensing and pricing. This is a product that I can recommend otherwise. I would rate this solution an eight out of ten.

My advice for anybody who is considering Apigee is that it is has a very easy and intuitive GUI to build APIs, and I can also import Swagger files. It is built on a high availability model, so if anything goes down then another node will automatically take over. We can build an active-active across the DR site. The primary site is active, the DR site is active, and they are synchronized. It is easy to build, customize, install, and implement. The support is also extremely good. We get immediate responses and support is available every day of the week. Google commits on the resolution time for priority-one issues as 24 hours. No other software today can commit to resolution time. I have only seen such a service with Google Apigee. Overall, I am satisfied with this product and it is aligned to all of my needs. I would rate this solution a ten out of ten.

We would definitely recommend Apigee. You can use Apigee to create proxies (and share API proxies with consumers), monitor calls, and provide security for particular endpoints. We have a complete telephone portal under Apigee, I would recommend it. I would give Apigee a rating of seven or eight out of ten. The API moderation, administration monitoring, product architecture, infrastructure, and overall quality is good. The only area lagging is integration capability.

My advice for anybody who is implementing Apigee is to use it as an API platform, and not as a full-stack integration platform. I would rate this solution a nine out of ten.

For on-premises I would not suggest this solution. Generally speaking, the product is a good one, it is matured and the features are okay. If anyone wants to use this solution they should first consider the cloud-based version. Because the support is lacking, we would have considered a different product. I would rate this solution a seven out of ten. If the support was better, I would have given them a nine.

Right now, we are still in the process of testing the solution. We're using both on-premises and cloud versions. CA has developed a sort-of enterprise service spot inside of their API management platform. It does interesting things with files, and it has a lot of security features that are not normally used in a majority of API calls. It's overkill. Its portal is very clunky and very difficult to set up. Its gateways and its policies are not straight forward either. It basically requires a three-day class to understand how to get in and add policies and it's not very simple to add policies into the CA Layer 7 gateway. Apigee does a way better job. CA is also owned by Broadcom now and when that transition happened, Broadcom did a lousy job of handing off support of that product. They basically fired everybody from CA. They left us without production support for a good part of a year. We've had CA for about 2 years and mostly we used the on-premises version, but we had a small amount on the cloud as well. Because of these reasons, we're moving away from Layer 7 to Apigee. In terms of advice to those considering using Apigee versus CA, I'd say they need to understand their use cases for APIs. I would rate Apigee eight out of ten. In comparison, I would rate CA five out of ten.