ProblemsFTS0058

Internal Calls Waste Capacity

Medium

Problem

Paradox Shop's checkout service calls the inventory service millions of times a day, but each call is tiny; a few bytes out, a few bytes back. Below, Service A calls Service B directly over plain HTTP with no pooling, and profiling shows the connection setup and header parsing cost more CPU than the actual work. Fix the call path: a faster protocol and connection reuse instead of a fresh handshake per call. Note that Connection Pool is reused here as a generic service-to-service pool between two application servers, not the database-tier component it usually is.

Required components

Click to add a component to the canvas.

Additional components

Browse by category. Click or drag a component onto the canvas.

Current Production Metrics
Snapshot of the system before any changes.
Traffic
4,000 calls/sec
Monthly cost
$660

Drag components from the library onto the canvas, then drag from a component's right handle to connect it to another.

100%

Design canvas

Sign up to start designing

Sign up free

Premium is free for 58 more days.