Apigee Edge is an API management platform now owned and offered by Google, since Google acquired Apigee in 2016.
N/A
Contentful
Score 7.6 out of 10
N/A
Contentful is a cloud based CMS solution that provides the ability to manage content across multiple platforms.The editing interface allows for managing content interactively and provides developers the ability to deliver the content with the programming language and template framework of their choice.
$0
Pricing
Apigee Edge
Contentful
Editions & Modules
No answers on this topic
Lite
$300
per month
Community
Free
Enterprise
Custom
Offerings
Pricing Offerings
Apigee Edge
Contentful
Free Trial
No
Yes
Free/Freemium Version
No
Yes
Premium Consulting/Integration Services
No
Yes
Entry-level Setup Fee
No setup fee
Optional
Additional Details
—
—
More Pricing Information
Community Pulse
Apigee Edge
Contentful
Features
Apigee Edge
Contentful
API Management
Comparison of API Management features of Product A and Product B
Apigee Edge
9.4
7 Ratings
11% above category average
Contentful
-
Ratings
API access control
9.07 Ratings
00 Ratings
Rate limits and usage policies
9.07 Ratings
00 Ratings
API usage data
9.07 Ratings
00 Ratings
API user onboarding
9.97 Ratings
00 Ratings
API versioning
9.97 Ratings
00 Ratings
Usage billing and payments
9.06 Ratings
00 Ratings
API monitoring and logging
9.97 Ratings
00 Ratings
Security
Comparison of Security features of Product A and Product B
Apigee Edge
-
Ratings
Contentful
8.5
10 Ratings
4% above category average
Role-based user permissions
00 Ratings
8.510 Ratings
Platform & Infrastructure
Comparison of Platform & Infrastructure features of Product A and Product B
Apigee Edge
-
Ratings
Contentful
9.5
12 Ratings
20% above category average
API
00 Ratings
9.311 Ratings
Internationalization / multi-language
00 Ratings
9.79 Ratings
Web Content Creation
Comparison of Web Content Creation features of Product A and Product B
Apigee Edge
-
Ratings
Contentful
7.8
13 Ratings
0% above category average
WYSIWYG editor
00 Ratings
7.34 Ratings
Code quality / cleanliness
00 Ratings
9.58 Ratings
Admin section
00 Ratings
9.311 Ratings
Page templates
00 Ratings
7.64 Ratings
Library of website themes
00 Ratings
7.52 Ratings
Mobile optimization / responsive design
00 Ratings
4.57 Ratings
Publishing workflow
00 Ratings
9.312 Ratings
Form generator
00 Ratings
7.01 Ratings
Web Content Management
Comparison of Web Content Management features of Product A and Product B
Few scenarios 1. For viewing API analytics, I think it is best in the market 2. For earning money via API monetization 3. Securing API 4. Onboarding legacy APIs to provide modern REST endpoints
It's a great all rounder for content projects. It's easy in the basics and powerful in the complex, data heavy scenarios. Extending the platform is straightforward and the SDK gives you everything you need. If you have many many varying content types , it gets expensive and perhaps not the best choice .
Prohibited from using JSON.stringify on Apigee objects (tokens)
Debugging is difficult
Unable to rename or delete policies without bumping revision
Why would anyone give a js policy one name, display name something else, and script a different name?
'Trace' limited to only 20 transactions
UI allows users to add target servers, but users must utilize the api to turn on SSL.
I'm sure there's more, they just aren't coming to mind right now.
Apigee forgets (expires?) your password at random intervals without notice. Every few weeks, or days, sometimes even three times in one day, I'll attempt to login to Apigee and my password will be 'wrong'. I've reset my password and Apigee still claims it's wrong. I've had to reset my password three times before it finally let me log back in.
Contentful uses "references" to allow you to build very modular content. If I have a "slider" content type, I can create a "slide" content type which references a "button" content type, and so forth. This works well, but I occasionally wish there was a better solution for one-off content, like a settings page. Currently, this is done for creating an entire content type called "settings" with a single entry. Not a big deal, but not ideal, either.
There are a few quirks with GatsbyJS integration, etc, but these issues are being fixed and improved upon very quickly.
A minor gripe, but Contentful does not have a way to organize fields within an entry. Entries with many fields are somewhat tiresome to scroll through.
I am not the one deciding whether to use apigee or not really. But personally, I would recommend the use of it as developing APIs on it is easy. And as a mediator between backend servers, we could easily modify request and responses in it without touching any backend code while having a centralize gateway to access our backend APIs too.
It is a very easy to use and configure application. I find that it is on the user to manage the content after the models have been created, yet I still do not encounter issues finding or creating new components for our site. It is easy to set up and easy to navigate.
Quite hard to get support, at least on the coding side, when we encounter blockers. But general concerns, they would schedule a call to you for them to get a whole picture of your concern. Albeit in my experience, bad really as they haven't replied about the progress, but otherwise seems to have been fixed.
Apigee is the best in the market in terms of API Analytics Apigee is having wonderful Documentation with short videos Security is a major concern and Apigee provides an easily configurable policy to secure API Quota and rate-limit is again very easy to configure on every API basis It provides various policies to transform the response from one form to another form e.g. JSON to XML or XML to JSON
Easy to use and much more organized as a single platform versus multi. The layout is clean and easy to read and we don’t have to worry about certain users safe guarding data or content then losing it when they leave the company. It’s a one stop shop for imagery
As a public entity it is hard to say how much ROI we can have. We have yet to create a billing and ROI plan. We are thinking of other ways to create ROI, possibly through data/service barter.
Contentful has saved us valuable development time that was previously spent doing deploys for minor content updates.
Contentful has helped us maintain consistent documentation, reducing time needed to review for consistency.
Can't say we've really experienced any negative ROI impacts from using Contentful, but we've run into some limitations in adding too many content models and the next pricing tier is substantially more expensive.