Story
F5
DatabricksDatabricks Uses NGINX for Edge Delivery
Databricks, an information technology organization in the United States, uses NGINX from F5 to support web performance for platform and web teams.
Value results
| Category | Value result |
|---|---|
| Productivity | Handoffs in web performance sit in a shared queue instead of a mailbox trail |
| Risk and compliance | NGINX is the governed place platform and web teams use for web performance |
| Capability | New joiners can see how web performance actually runs |
Story
Inside Databricks, web performance used to depend on whoever still had the latest file. That pattern is common in information technology groups working out of the United States. Platform and web teams needed a system that would still make sense after the original project team moved on.
Databricks uses NGINX from F5 as the working layer for edge delivery. F5 provides application delivery, security, and traffic management products used in front of enterprise applications. The practical change is simple: web performance has a home, and reviews happen there instead of in a forwarded thread.
Nothing in this writeup invents a savings number. What Databricks gets from F5 is a durable place to run web performance and a way for platform and web teams to see the same edge delivery at the same time.
