How we built the Traffic Policy module and its actions

Ngrok has introduced Traffic Policy, a feature that enhances the flexibility and control developers have over the traffic to and from their applications and APIs, using the Common Expression Language (CEL) for detailed traffic manipulation. This innovation addresses previous challenges with ngrok's module system, which required cumbersome configurations and lacked the ability to conditionally apply rules based on traffic attributes like paths or headers. Traffic Policy allows for programmable expressions to be applied at different phases of traffic handling, such as when a connection is established or during HTTP requests and responses, enabling more nuanced and efficient traffic management. The new system also simplifies the process of updating and deploying traffic policies without extensive changes to SDKs or applications, as it moves away from rigid structures to more flexible string-based configurations. As ngrok continues to integrate old module functionalities into Traffic Policy, they are also exploring new capabilities such as action chaining, specific service routing, and global security policy configurations, all aimed at making it easier and safer for developers to bring their services online without deep networking expertise. With Traffic Policy now generally available, ngrok invites users to explore its potential, offering free initial requests and extensive documentation to support developers in shaping their traffic effectively.

No tracked trend matches for this post yet.

Use this post, company, and trend context to find content marketing opportunities, perform competitive analysis, or address product feature gaps via the Plushcap MCP server or the Plushcap API.