ProblemsML0015

Freshness SLAs Differ by Feature

Medium

Problem

Three teams share one feature platform: fraud scoring needs 10-second freshness, recommendations tolerate 15 minutes, and finance runs a nightly batch report that only needs a 12-hour window. Today one pipeline refreshes everything every 10 seconds to satisfy fraud, and the compute bill is absurd; recs and finance are paying hot-path prices for data that barely changes. Design the platform so each tier gets exactly the freshness it needs, sharing one set of feature definitions instead of three teams each maintaining their own copy.

Required components

Click to add a component to the canvas.

Additional components

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

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.