F5 Distributed Cloud App Connect vs. SAP Business Rules Management

My advice is if your firm build multi-cloud, high availability SaaS products or you just run polyglot workloads across kubernetes and VMs, then F5 Distributed Cloud App Connect is your guy. Coming from an expert, just start with a few core services or else you will be overwhelmed.

Incentivized

• Ease of use - standing up a new site took very little time, less then an hour.
• Connecting the dots - the ease at standing up a load balancer and advertising it on CEs was simple and straight forward. Once you get familiar with the field layout it's very comparable to BIG-IP

Incentivized

• User access roles should be more granular what we currently have
• user interface should be user friendly
• Setup process and guided workflows could add a user friendly process for first time users
• log export from SIEM tool still require a manual intervention

Incentivized

At this point it has become too focal to our operations. An entire department could collapse if we dropped it now or in the near future. My experiences as mentioned in the previous questions tell of its gravity

Incentivized

From what we have been able to test load/responsiveness is quick and when we've tested out reporting and troubleshooting modules they have pulled the correct information in quick timeframes. We haven't been able to test out any software integration with Splunk of other software on our system since we are still in early POC stages but from what we've been told we should be able to implement that in our environment

Incentivized

-F5 Distributed Cloud App Connect provides more granular security policies with features like DOS, WAF etc and others lack -F5 Distributed Cloud App Connect provides high performance global network and other rely on public internet and impact is latency and it gives F5 Distributed Cloud App Connect a better user experience

Incentivized

• Inconsistent policies and procedures and now its all seem to be sorted and now requires less support
• Deployment cycle time was reduced and achieves a faster adoption of newly added contents
• Saved migration cost and more gave durability to the existing setup

Incentivized