Not just another variant in the ever-growing set of "X-Ops" practices, Platform Ops is a way to balance developer freedom and corporate compliance for technology teams across the enterprise, helping you achieve digital transformation with the right blend of shifted left and buttoned down.
Strategies for shifting security left usually ignore WAF and other traditional tools for enforcing run‑time security policies. A complete modern solution needs to include WAF, but one that fits into your CI/CD pipelines and helps smooth friction between Security and DevOps.
The modern market's demand for speed has heightened the tension between DevOps and NetOps/SecOps teams. But you can have both developer productivity and infrastructure reliability -- bridge the divide with self-service app delivery tools from NGINX.
Automation is essential to delivering modern digital experiences. We've created four video demos showing how to automate deployment of NGINX Plus and NGINX App Protect, NGINX Controller, an NGINX Plus data plane using Controller, and GSLB using F5 DNS Cloud Services.
As use of DevOps practices grows, traditional API management solutions are failing to provide the tools for creating modern digital experiences powered by APIs. NGINX Controller is built for DevOps, with a decoupled design that decreases latency, multi-cloud support, self-service, and more.
Application security is hard, but there are some best practices to help you achieve it: automate as much as possible, build security as a guardrail instead of a gate, select solutions that provide easily understood insights, and make security adaptable, scalable, and reliable.
We provide guidance on where to deploy application services in a Kubernetes environment, using WAF as an example. Depending on your needs, it can make sense to deploy your WAF at the "front door" of the environment, on the Ingress Controller, per-service, or per-Pod.
We explain why duplicating application services paradoxically can improve overall efficiency: because NetOps and DevOps teams have different mandates, it makes sense for them to select and manage the tools that best suit their specific needs.
The F5 and NGINX control-plane development teams recently integrated their code development practices and tools. They chose GitLab for the code repository, GitLab CI for the development pipeline, and JFrog Artifactory for artifact storage.