Story
How Docker Runs Network Operations on F5 Distributed Cloud
Docker, an information technology organization in the United States, uses F5 Distributed Cloud from F5 to support network operations for network engineers.
Value results
| Category | Value result |
|---|---|
| Capability | Network engineers work from the same F5 Distributed Cloud record for campus and branch networking |
| Capability | Campus and branch networking can be reviewed without waiting on a personal export |
| Capability | Named workflow replaces ad hoc routing for campus and branch networking |
Story
Information Technology work at Docker spans more than one site, even when headquarters sits in the United States. Campus and branch networking was splitting across regional habits. Network engineers asked for a shared way to run network operations without freezing local judgment.
F5 (F5 Distributed Cloud) is what they standardized on. F5 provides application delivery, security, and traffic management products used in front of enterprise applications. Docker uses it as the system of record for campus and branch networking, with network engineers as the primary operators and other groups coming in through the same queue.
Leaders get a picture they can actually walk. Teams get fewer mystery statuses. The story is about operating change, not an unpublished percentage.