I need to think about this for the future. F5 Distributed Cloud Services needs to create links with Amazon and Google Cloud or other platforms. At this moment, it does not have integrated steps to work with those clouds. I think in the future, F5 Distributed Cloud Services needs to create these links with other clouds to work more reliably. I think the APIs and synchronization with other clouds or systems with OCI to Oracle needs to be implemented for the future. More integration options are needed. The offering in Mexico has a lot of traffic to Amazon or Google Cloud or Microsoft Azure. I need to integrate this solution with F5 Distributed Cloud Services and the reliable services and application delivery services. The worst experience is that with so many solutions available, it is very complicated to know all of the solution modules, and the offers from F5 Distributed Cloud Services are vast. It is complicated to know all the solutions regarding security with WAF, delivery controller with LTM, ACM, as F5 Distributed Cloud Services really has a lot of modules.
There are some gaps between the implementation, expectation, and the reality. The main point is user integration with other parts, such as on-premises. One thing is on-prem and the other one is on the cloud. It is sometimes difficult to implement or execute and bring that onto the same page. This is one thing I would say requires improvement and definitely they can solve this. Basically, this is a critical concern. For one thing, if the organization does not need the complete bundle, it comes with huge costing included if you're putting something in a bundle. For example, one organization needs only a simpler use case, for example a CDN with very lightweight sort of security. I'm talking about very small organizations. For them, it is huge costing because they have to buy a complete bundle. They should have what CloudFlare provides, which is a simple CDN feature and API security that is very cheap and affordable. F5 Distributed Cloud Services doesn't have something like that. That is the reason why CloudFlare remains a leader in that space for small customers and those who have just started or are startups. That is one thing that can definitely be worked on. It is because there are other players in the market that provide very cheaper and simpler environments or infrastructures, CloudFlare and Akamai. Comparatively, F5 Distributed Cloud Services is relatively much more expensive.
Last year there was a downtime of 30 minutes across the cloud distributed console, and that was the only impact observed. Since 30 minutes of downtime is huge for applications, maintenance, it impacted RPO, RTO, and all. The F5 CTO and their senior management team addressed that issue. For availability, they have added additional clusters across all the regional edges in the Kubernetes clusters to enhance availability. However, this improvement needs to be monitored since it was a past incident.
It's a long way to be perfect, of course, as with all solutions. The main issue is integration with other parts or products of F5, like on-premise WAF. There are some problems, mainly from the perspective of implementation and customer expectations, which sometimes differ from reality.
F5 Distributed Cloud Services excel in enhancing security, optimizing web application delivery, and ensuring robust network performance. Users value its integrated Web Application Firewall, DDoS protection, global server load balancing, and intuitive management interface. It boosts organizational efficiency, reduces operational costs, and scales seamlessly, making it essential for businesses operating in distributed environments.
I need to think about this for the future. F5 Distributed Cloud Services needs to create links with Amazon and Google Cloud or other platforms. At this moment, it does not have integrated steps to work with those clouds. I think in the future, F5 Distributed Cloud Services needs to create these links with other clouds to work more reliably. I think the APIs and synchronization with other clouds or systems with OCI to Oracle needs to be implemented for the future. More integration options are needed. The offering in Mexico has a lot of traffic to Amazon or Google Cloud or Microsoft Azure. I need to integrate this solution with F5 Distributed Cloud Services and the reliable services and application delivery services. The worst experience is that with so many solutions available, it is very complicated to know all of the solution modules, and the offers from F5 Distributed Cloud Services are vast. It is complicated to know all the solutions regarding security with WAF, delivery controller with LTM, ACM, as F5 Distributed Cloud Services really has a lot of modules.
There are some gaps between the implementation, expectation, and the reality. The main point is user integration with other parts, such as on-premises. One thing is on-prem and the other one is on the cloud. It is sometimes difficult to implement or execute and bring that onto the same page. This is one thing I would say requires improvement and definitely they can solve this. Basically, this is a critical concern. For one thing, if the organization does not need the complete bundle, it comes with huge costing included if you're putting something in a bundle. For example, one organization needs only a simpler use case, for example a CDN with very lightweight sort of security. I'm talking about very small organizations. For them, it is huge costing because they have to buy a complete bundle. They should have what CloudFlare provides, which is a simple CDN feature and API security that is very cheap and affordable. F5 Distributed Cloud Services doesn't have something like that. That is the reason why CloudFlare remains a leader in that space for small customers and those who have just started or are startups. That is one thing that can definitely be worked on. It is because there are other players in the market that provide very cheaper and simpler environments or infrastructures, CloudFlare and Akamai. Comparatively, F5 Distributed Cloud Services is relatively much more expensive.
Last year there was a downtime of 30 minutes across the cloud distributed console, and that was the only impact observed. Since 30 minutes of downtime is huge for applications, maintenance, it impacted RPO, RTO, and all. The F5 CTO and their senior management team addressed that issue. For availability, they have added additional clusters across all the regional edges in the Kubernetes clusters to enhance availability. However, this improvement needs to be monitored since it was a past incident.
It's a long way to be perfect, of course, as with all solutions. The main issue is integration with other parts or products of F5, like on-premise WAF. There are some problems, mainly from the perspective of implementation and customer expectations, which sometimes differ from reality.
The pricing could be adjusted to better meet the needs of typical customers in regions like Poland, where the product is considered too expensive.