Cracking the Code: “Steve's Number of Zeros”for Estimating Integration Volumes! (in English)
Updated 2026-11-07
What's changed since the video
Each change is dated and checked against Salesforce's own documentation.
- Three spoken numbers to correct. Not a platform change: arithmetic. For the trucks, 40,000 transactions averaging about 1.5 MB in an 8-hour window is about 2 MB a second, not "two gigs". For the appointments, 300,000 of about 100 KB over 11 hours is about 0.76 MB a second, not "73 Megs". For the call center, the records per second are 5 (1.67 transactions a second, 3 records each), not four; its bytes per second need a transaction size the video doesn't give.
- The courses work it from the scenario. Integration Architect chapter 6 and Data Architect chapter 9 teach the same method with Steve Trucking's own numbers, and check each step.
Still right
- The method: start from the business's rough numbers, aim slightly higher, and turn them into transactions per second, records per second and bytes per second over the hours the work really happens.
- The four worked examples: opportunities to an ERP, truck deliveries with photos, store appointments, and a call center. The transactions-per-second figures in the video check out (0.84, 1.39, 7.58 and 1.67).
- Do the math early, before anyone picks a mechanism.
All videos in this series: ארכיטקטורת אינטגרציה
סרטון נטען מ-YouTube רק כשלוחצים עליו.