A token bucket can help protect Hyperledger Fabric endorsing peers from excessive request rates, but it is an external control pattern—not a native Fabric setting documented in the official materials reviewed. Fabric’s peer concurrency limits are a separate mechanism: they cap simultaneous requests, not requests per second. To avoid disrupting transactions, size and place any limiter around the endorsement policies your network must satisfy, then tune it against measured workload and capacity.
Why endorsement traffic needs policy-aware limits
Endorsing peers execute chaincode and return signed results. An endorsement policy specifies which peers must endorse a transaction for it to be valid. A limiter that blocks a peer required by that policy can prevent the client from collecting the endorsements needed to proceed, even if the peer itself is healthy. See the Hyperledger Fabric endorsement policies documentation and the project’s security model.
As an Amazon Associate I earn from qualifying purchases.
That makes rate limiting more than a matter of reducing load. The control must protect service capacity without making the required endorsement set unavailable to legitimate transactions.
Does Fabric have a built-in token-bucket limiter?
The reviewed official Fabric documentation describes peer concurrency controls, but does not document a native token-bucket rate limiter for endorsement peers. Treat a token bucket as a separately deployed application-, gateway-, or proxy-layer design, and verify that the component you choose provides the rate, burst, and exhaustion behavior your workload needs.
#1 Best Overall
- Compact and Efficient Design: The FortiGate 40F is designed for small to mid-sized businesses and enterprise branch offices, featuring a compact, fanless desktop form factor that ensures quiet operation and minimizes space usage.
- Robust Connectivity Options: Equipped with 5 GE RJ45 ports, including 1 WAN port and 4 internal ports, this model provides essential connectivity and flexibility for various network configurations in a small-scale environment.
- High-Performance Security: Offers up to 1 Gbps IPS throughput and 600 Mbps threat protection throughput, using Fortinet’s purpose-built security processor technology to deliver industry-leading performance and protection for SSL encrypted traffic.
- Advanced Threat Protection: Integrated with Fortinet’s AI-powered FortiGuard Labs, the FortiGate 40F offers comprehensive cybersecurity, identifying and mitigating both known and unknown threats to maintain robust security across your network.
- Simplified Management and Deployment: Features a user-friendly management console that provides comprehensive network automation and visibility, coupled with Zero Touch Integration with Fortinet’s Security Fabric for easy deployment.
Fabric’s sample peer configuration describes peer.limits.concurrency as a limit on concurrent requests. It currently applies to endorser and deliver services; a value of zero or an unset value disables the service limit. These settings are not a token rate. Consult the official sample peer configuration for the target release.
Concurrency limits and rate limits solve different problems
A concurrency cap limits how many requests are in flight at one time. A rate limiter controls how quickly new requests are admitted over time. They can be used together, but a value for one cannot be substituted for the same number in the other.
| Control | What it limits | What it does not establish |
|---|---|---|
| Peer concurrency cap | Simultaneous requests in the covered service | A tokens-per-second rate or a burst allowance |
| Token bucket | Average admission rate, with a bounded burst determined by its capacity | The maximum number of requests that may remain in flight |
The Fabric performance guide lists example peer service concurrency values of endorserService: 2500, deliverService: 2500, and gatewayService: 500. These are documented configuration examples, not universal recommendations or token rates. The guide notes that the peer Gateway Service was introduced in Fabric v2.4 and that its default can restrict network TPS in some situations. Check the configuration and guidance for the exact Fabric release you operate: Hyperledger Fabric performance guide.
Free tools Windows power users keep installed
One-click scans. No signup required.
Rank #2
- HARDWARE PLUS SECURITY SERVICES: FortiGate-60F Firewall Appliance bundled with 1 year of FortiCare Premium and FortiGuard Unified Threat Protection.
- UNIFIED THREAT PROTECTION (UTP): Secures against advanced online threats with comprehensive web filtering and anti-botnet technologies.
- OPTIMIZED FOR MEDIUM-SIZED BUSINESSES: Tailored for businesses needing robust security without the infrastructure of larger enterprises.
- RELIABLE CUSTOMER SUPPORT: FortiCare Premium ensures high-quality support and service continuity.
- EFFECTIVE PROTECTION: Employs advanced filtering technologies to safeguard against sophisticated threats.
How a token bucket works
A token bucket replenishes tokens at a configured rate, up to a maximum capacity. An admitted request consumes tokens. If a request arrives when there are not enough tokens, the implementation may reject it, delay it in a queue, or shed load; the choice depends on the limiter.
The replenishment rate governs sustained admission, while bucket capacity governs how much short-term burst traffic can pass. There is no universal Fabric-specific rate or burst size established by the cited documentation. Choose both from observed request patterns and peer capacity rather than treating the performance guide’s concurrency examples as sizing guidance for a token bucket.
Where to place the limiter and how to scope it
A client-facing API layer or reverse proxy can shape inbound proposal traffic before it reaches a peer. A Fabric-aware gateway or application can make more selective decisions by client identity, channel, chaincode, or operation—but only if it can reliably observe those attributes. These are architectural options, not components endorsed by Fabric’s official documentation.
Rank #3
- 【Up to 1100 Mbps VPN Speed 】 Hardware-accelerated WireGuard and OpenVPN-DCO deliver up to 1100 Mbps VPN throughput, over 3× faster than Brume 2 for smooth remote access and file transfers.
- 【Three 2.5G Ports & Multi-WAN】Tri-port 2.5GbE design with flexible WAN LAN configuration supports multi-gigabit wired setups, dual-ISP Multi-WAN and failover to keep home and SOHO networks online.
- 【Stealth VPN Obfuscation】VPN obfuscation disguises VPN traffic as regular HTTPS, helping you evade blocking, bypass restrictive networks and maintain stable, private connections.
- 【DPI protection】Deep Packet Inspection with visual dashboards blocks adult/gambling/malicious sites, while SQM and QoS prioritize gaming, calls, and video when bandwidth is tight
- 【OpenWrt & USB 3.0 Expansion】OpenWrt with 1GB DDR4 and 8GB eMMC lets you install plugins and build VPN, ad-blocking or NAS, while USB 3.0 Type‑C connects high-speed storage or 4G/5G dongles
- Shared limit: A single pool can protect aggregate service capacity, but it can also concentrate failure if the limiter becomes unavailable or is misconfigured.
- Per-client limit: Separate budgets can reduce noisy-neighbor effects, but depend on trustworthy client identity mapping.
- Organization-wide limit: A broad limit across an endorsement organization can affect multiple peers that transactions may need to satisfy policy requirements.
- Channel-, chaincode-, or operation-specific limit: Finer scoping may better reflect workload differences, provided the component can identify the relevant traffic correctly.
When evaluating an implementation, establish whether it supports the intended rate and burst semantics, how it scopes budgets, what it does when exhausted, and what happens if the limiter itself is unavailable. Also require visibility into delayed and denied traffic so operators can distinguish deliberate shaping from peer or network failure.
The Tool Desk
Outbyte Driver Updater FREEFix the driver behind crashes, sound loss and screen glitchesFind Drivers →Outbyte PC Repair FREERepair Windows errors before they cause bigger problemsFix Now →Account for Gateway retries and timeouts
Fabric Gateway uses discovery information to retry failed requests across eligible peers or organizations under documented failure conditions. Its endorsement and broadcast timeouts are configurable. A limiter can therefore affect more than the first request: rejections or delays may increase retry activity, extend client latency, or prevent the client from collecting enough endorsements to meet policy. Review the Fabric Gateway documentation when setting limits and timeouts.
Observe the limiter alongside Gateway retry counts, endorsement success, client latency and errors, peer CPU and memory use, and queue or in-flight request levels. Fabric’s performance guidance calls for monitoring resources and adjusting when thresholds are exceeded; exact metrics and thresholds depend on the deployment. Avoid assuming that retries always provide a safe fallback: policy requirements and the peers eligible to satisfy them determine whether another attempt can succeed.
Roll out limits using measured workload
- Establish a baseline. Measure request volume, burst patterns, endorsement success and latency, peer resource use, and existing concurrency or queue pressure before adding a rate limit.
- Map policy dependencies. Identify which peers and organizations are required for the endorsement policies used by the affected transactions. Ensure the limiter cannot systematically starve those paths.
- Choose placement and scope. Decide whether to shape traffic at a client-facing layer or in an application or gateway with relevant identity and transaction context. Define what happens when the limiter is exhausted or unavailable.
- Start conservatively and observe. Set rate and burst capacity from measured demand and available peer capacity. Watch denials and delays alongside retry behavior, endorsement outcomes, client latency, and peer load.
- Adjust based on outcomes. If load remains high, tune the external rate control and review the peer’s concurrency settings for the deployed release. If valid transactions are delayed or failing to gather endorsements, investigate the limiter’s scope and exhaustion behavior as well as Gateway retries and timeouts.
This is general operational guidance, not a tested Fabric benchmark. The right settings depend on the transaction mix, endorsement policies, deployment resources, and the specific limiter implementation.
Quick Recap
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
