๊ฐ€์ž… ํ›„ ์ดˆ๋Œ€ ๋งํฌ๋ฅผ ๊ณต์œ ํ•˜๋ฉด ๋™์˜์ƒ ์žฌ์ƒ ๋ฐ ์ดˆ๋Œ€ ๋ณด์ƒ์„ ๋ฐ›์„ ์ˆ˜ ์žˆ์Šต๋‹ˆ๋‹ค.

cv usk
@cv_usk
AI / Software Research Notes AI Agent, LLMOps, MLOps, Software Architecture ๆŠ•็จฟใฏๅ€‹ไบบใฎๆ„่ฆ‹ใงใ™ใ€‚
๊ฐ€์ž… May 2026
286 ํŒ”๋กœ์ž‰ ์ค‘    469 ํŒฌ
TL;DR Uber Freight supports search across 40+ microservices and nearly 100 data sources by composing one shared index from independently owned fragments. Title: Freight Search: Composing a Shared Search Index from Independently Owned Fragments URL: Key points ใƒป๐Ÿงฉ Each index field comes from exactly one fragment, so ownership never conflicts ใƒป๐Ÿงฑ Fragments merge into one denormalized document, so queries need no joins ใƒปโš™๏ธ Spark handles bootstrap; Flink with CDC handles live ingestion, with changes searchable in seconds ใƒป๐Ÿท Mappings are generated from Java annotations, so the class is the single source of truth ใƒป๐Ÿ”— Declare @/LinkedEntity or a fold function and the platform handles parent-child denormalization and 1:N aggregation ใƒป๐Ÿ”„ The SIA-to-OpenSearch migration touched only a few places and applied to every entity ใƒป๐Ÿ“ˆ About 300 fragments across 20+ indices, thousands of queries per second, p99 in hundreds of milliseconds Separating business definitions from platform internals is what let the design survive an engine migration. #Uber# #SearchInfrastructure#
๋” ๋ณด๊ธฐ