Amazon CloudFront is the perfect solution for any type of company. If a company is small or medium size, CloudFront offers 1 TB monthly free bandwidth which is more than for any small and medium size companies. If we compare the speed of CloudFront with other CDN, CloudFront is way ahead of their competitors and with 1 TB free bandwidth. If someone is ready to invest time in CloudFront documentation then he/she definitely go for it.
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
if a website’s static data are based in New York City, people in Boston will get the content faster than people in San Francisco or Tokyo. The farther away customers are from a company’s data center, the slower the website or application loads. This problem can be fixed with a content delivery network like Amazon CloudFront
When a visitor requests a file from your website, Amazon CloudFront automatically sends the request to a copy of the file at the nearest edge location. This results in faster download times.
You may have great hosting but it doesn’t have the capacity or scalability offered by Google, Microsoft or Yahoo. The better CDNs like Amazon CloudFront offer higher availability, lower network latency and lower packet loss.
Amazon CloudFront provides 24/7 email and phone support
Amazon CloudFront Free Tier allows you to free up to 50 GB of data transfer and 2,000,000 HTTP and HTTPS requests / month for one year.
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.
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.
CloudFront is a good CDN solution. It can be a bit complicated to implement depending on your needs, but AWS tech support is great. You get to avoid a ton of upfront costs by going with CloudFront. It works best in conjunction with other AWS services in your infrastructure. Once you set it up, you won't need to do much to maintain it. It just works.
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.
Amazon has always been creative and leading, and I have been using its services for years. They are very reassuring and have fast and responsive support--you can call them from any time zone to respond quickly. High security on servers, open hands on changes, and increasing and decreasing server resources and features.
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
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.