The product's scalability can be improved since certain shortcomings regarding the security part of the solution currently exist.

Up-and-coming CDNs are coming into the market to compete with more established vendors like Akamai. They're competing in areas specific to edge computing. I want to see the product increase in innovation and activity in that area. I'd like to see improvements in log files and data visualizations within the interface.

For Akamai, it is definitely one of the best tools out there. However, there are challenges with how their approach is designed for large enterprises.

While it's great for solutions with high scalability, like global e-commerce, it's not really built for small and medium-sized businesses (SMBs). It has too many options and can be complex for SMBs to utilize.

That's the biggest challenge we faced when migrating to Akamai from other solutions, like Cloudflare. It can be difficult to migrate between platforms.

Due to its great features but high activation thresholds. So, while it's a powerful tool, it has limitations for some implementations.

It was difficult to migrate from and to Akamai. It is challenging when we are building a website.

From my perspective, there are a few areas that need improvement, especially in terms of security upgrades. Currently, Akamai does not provide the same level of security as Cloudflare, which supports applications through SSL HTTPs. This is one aspect that needs attention. 

Another aspect is the pricing. Akamai should target mid-level and small to medium-sized businesses, not just enterprise-level companies. The larger companies already benefit from it, so it shouldn't be the sole focus. We should focus more on medium-sized businesses as well. 

Mostly, I would like to see improvements in the security aspect. The web application firewall needs to be enhanced and offers more customization options. Additionally, while there are many available servers, they come as add-ons. This limits our ability to explore all the features, as they require additional payments.

As Akamai offers rule-based protection, the rules have to be configured on priority and should be done at the earliest since new development keeps taking place. Akamai's configuration part is an area of concern where improvements are required to make the process easy.

In Akamai, one should be able to change the rules in the rule-based protection. Traffic filtering is an area in the solution that has to be updated to the latest one to be possibly active to manage the latest and upcoming attacks.

The solution can be more specific regarding the alerts it gives. Currently, we have to check each and every traffic for every IP. It would be better if we could be notified about specific attacks.

I can't point out any downsides of Akamai since it is presently one of the best solutions in the market.

In our company, we are good with how the solution works for us since we continuously use it to improve our processes.

New features will keep getting added to the product as the needs of businesses or organizations grow, making it a never-ending process.

The fact that it is an expensive product is its only shortcoming. The pricing of the product can be made better.

I'd like to see more Web 3.0 and IoT solutions. 

The user console is quite overloaded, sometimes it's hard to find your way around.

With regards to additional features, Akamai continues to buy other companies and integrate their services into their product. It's kind of like a big bouquet of solutions and it would be good to see this continue in the future. From experience, sometimes you have different user consoles from the same supplier and that makes it hard to keep an overview and have reporting of everything in one place. 

If you ask about Akamai as a whole, then I would say that there are a lot of areas where improvements are required. In general, there are a few areas where I really think that Akamai's services need improvement. In Akamai, as far as CDN is concerned, I feel that its features are an area where some improvements or upgrades are required. Caching strategy is an area with certain shortcomings in the solution where improvements are required. Suppose you are using a feature called cache tags, which are basically a set of tags that are used to represent certain elements in the URL. When you use cache tags, you can flush out cache or parts of it or all the URLs that are associated with that tag. Akamai doesn't have a feature to cache the tag, as it currently has the feature to purge the cache in the tag. Akamai currently doesn't have a feature with which you can get all the URLs based on the tag and then apply some caching on top of it, making it a feature that Akamai lacks.

The solution could offer more integrations. 

Akamai could improve by providing its own cloud services. We have to use third-party cloud services at this time, such as Amazon AWS. The offering becomes a lot easier for an SMB if everything was in one single platform to be used for the services.

Akamai should improve its integrations. 

One area for improvement with Akamai could be pricing.

The solution can be improved by creating a communication pathway with technical engineers because when we open tickets, we have a delay in response times.

Local connectivity would be great linked to our own telecom/Cablevision CDN, as we are a key player for Internet access in Argentina for final users of mobile, DSL, cable, and FTTH users.