All Products
Search
Document Center

Microservices Engine:Overview

Last Updated:Oct 23, 2024

The traffic protection feature takes traffic as the starting point, ensures service stability in multiple dimensions, such as throttling, circuit breaking and degradation, and system overload control, provides professional and stable traffic protection measures, and analyzes traffic distribution within seconds. The traffic protection feature is the core component of the technical system that is used for online promotion activities such as Double 11 and is a commercial product of the open source framework Sentinel.

Scenarios

The traffic protection feature is widely used in various scenarios, such as flash sales, peak-load shifting for messages, cluster throttling, and real-time circuit breaking, to ensure the stability of your business in multiple dimensions.

The traffic protection feature is used in a common distributed application. Before a request from a terminal reaches the frontend network service, the request reaches the gateway and then passes through the firewall and Network Load Balancer (NLB). During the process, downstream services and third-party applications are called. Traffic protection provides real-time traffic analysis within seconds at different levels. For example, this feature provides real-time traffic monitoring and traffic diagnosis and analysis at the client level. This helps O&M personnel take preventive measures to protect the stability of applications.

Features

  • The second-level traffic analysis feature is supported and dynamic rules can be pushed in real time.

  • Professional and diversified preventive measures are provided:

    • Ingress throttling: Throttling is performed based on the service capacity, which is commonly used for application ingress, such as gateways, frontend applications, and service providers.

    • Concurrency isolation: The maximum number of concurrent threads is limited to prevent slow calls from occupying resources such as a thread pool for a long period of time. This ensures that resources are available over other interfaces.

    • Hotspot isolation: Hotspots are isolated from normal traffic. This prevents invalid hotspots from preempting the capacity of normal traffic.

    • Circuit breaking on dependent applications: Circuit breaking is applied between applications and within an application. This minimizes the impact of unstable dependencies on applications and ensures application stability.

  • The real-time single-node monitoring capability is supported to provide powerful aggregate monitoring and historical data monitoring and query capabilities.

References

For more information about Sentinel, see Sentinel.