4) Guardrails and Metrics

Guardrails• Batch sizes and concurrency caps to protect backend systems.• Time windows (nightly full, business-hours deltas).

Config

Memory

Hit Rate

ERP Calls Saved

Revenue Coverage

90%+ Customers

Calls/MB

1000 × 50

24.4MB

59%

196,493

88%

394 (39%)

8,053

1000 × 40

19.5MB

53%

178,880

88%

310 (31%)

9,173

1000 × 30

14.6MB

47%

156,831

221 (22%)

10,742

1000 × 25

12.2MB

43%

143,337

175 (18%)

11,749

400 × 50

9.8MB

56%

93,374

79%

136 (34%)

9,528

Legend:

• Config: The caching strategy: [Number of top customers] × [Products cached per customer]• Memory: Total memory required to store the cache in production• Hit Rate: Percentage of order lines that will be served from cache instead of calling ERP• ERP Calls Saved: Absolute number of product availability/pricing calls eliminated over 12 months• Revenue Coverage: Percentage of total revenue generated by customers included in the cache• 90%+ Customers: Number (and %) of customers who experience elite performance (90%+ cache hits)• Calls/MB: Efficiency metric: ERP calls eliminated per megabyte of memory used

Recommended Configuration: 1000 × 50

Highest hit rate and most ERP calls eliminated - 394 customers receive premium experience - Covers 88% of revenue base - Memory investment: 24.

Bridgestone