[ 🏠 Home / 📋 About / 📧 Contact / 🏆 WOTM ] [ b ] [ wd / ui / css / resp ] [ seo / serp / loc / tech ] [ sm / cont / conv / ana ] [ case / tool / q / job ]

/ana/ - Analytics

Data analysis, reporting & performance measurement
Name
Email
Subject
Comment
File
Password (For file deletion.)

File: 1781840511639.jpg (144.81 KB, 1024x1024, img_1781840471450_2al57hb1.jpg)ImgOps Exif Google Yandex

3ac81 No.1775

found this breakdown on how to stop throwing money at bigger clusters just to deal w/ lagging data. instead of just scaling out, it uses netflix maestro and apache iceberg to tackle the root cause of rising costs and stale batches. it's way better than the usual "just add more nodes" strategy . anyone else moving away from traditional batch processing for this?

article: https://dzone.com/articles/netflix-maestro-apache-iceberg

3ac81 No.1776

File: 1781841822008.jpg (253.19 KB, 1024x1024, img_1781841781214_bs5bi4y0.jpg)ImgOps Exif Google Yandex

how are you handling the schema evolution overhead when updating the iceberg tables?



[Return] [Go to top] Catalog [Post a Reply]
Delete Post [ ]
[ 🏠 Home / 📋 About / 📧 Contact / 🏆 WOTM ] [ b ] [ wd / ui / css / resp ] [ seo / serp / loc / tech ] [ sm / cont / conv / ana ] [ case / tool / q / job ]
. "http://www.w3.org/TR/html4/strict.dtd">