A really powerful multi-cloud mesh
Use Cases and Deployment Scope
Most of our clients operate in fragmented environments: GCP for ML workloads, aws for backends and on-prem databases. So we are using F5 Distributed Cloud App Connect to stitch these services together securely and consistently across environments. We are also using it to standardize zero-trust security policies across workloads. But this is mostly for clients in fintech and healthcare.
Pros
- It's so good at multi-cloud service sprawl. Most clients don't want to be locked into a single cloud and that's where F5 Distributed Cloud App Connect thrives. It is the true unifying fabric.
- Another one is fragile edge failover and routing.
- A good access drift between environments.
Cons
- Right now, the documentation leans toward abstract explanations and often leaves gaps when implementing more advanced routing topologies.
- The terraform provider is decent but inconsistent
Most Important Features
- The full observability into service flows
- Service meshes
- Standardization of zero-trust security policies
Return on Investment
- It has cut down engineering time for fragile edge failovers by over 40 percent - on high availability setups
- An overall lowered cost of ownership for cloud networking, i estimate it to be around 20%
- Reduced deployment complexity by half
Alternatives Considered
AWS App Mesh and Azure Service Fabric
Other Software Used
AWS CloudFormation, Azure AI Studio, (EOL) Cisco CloudCenter




