对于开发人员和DevOps来说，未来就是现在。了解这些将要改变世界的技术。
为什么每个公司都需要平台运营（Platform Ops）
平台运营不仅仅是数量不断增长的“XX运营”实践的又一种变体，还是一种可以在开发者自由和适用于企业中多个不同技术团队的规章制度之间取得平衡的方式。它可以帮助您在安全“左移”和传统组织架构之间取得完美平衡，从而实现数字化转型。
将安全防护工具左移，让应用更安全
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.
NGINX Controller 助力 DevOps 的 API 管理
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.
在 Kubernetes 中部署应用交付服务（第 2 部分）
在这篇文章中，我们以 WAF 为例，为您提供了“在 Kubernetes 环境中可以在哪些地方部署应用服务”的相关指导。您可以根据自己的需求，以基于每个 Service 或基于每个 POD 的方式，将 WAF 部署在 Kubernetes 环境的“前门” 或 Ingress Controller上。
在 Kubernetes 中部署应用交付服务（第 1 部分）
这篇文章解释了为什么因分治而重复使用的应用服务反而可以提高整体效率：因为 NetOps 和 DevOps 团队有不同的要求，所以他们会选择最适合他们特定需求的工具。
DevOps 实操：将 NGINX Controller 的开发转移到 GitLab CI
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.
