[ 🏠 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: 1781477323136.jpg (112.71 KB, 1024x1024, img_1781477315640_6vhpre54.jpg)ImgOps Exif Google Yandex

fd776 No.1756

been thinking abt how many people treat redshift like a bottomless pit for every single dataset. you rly don't need to load five-year transaction histories directly into local tables if they aren't being queried constantly. i've been playing around w/ an architecture using apache iceberg on s3 combined with redshift spectrum to keep the warehouse lean. it lets you move the heavy, cold data out of the cluster while still keeping it accessible via the same interface. it basically turns your warehouse into a managed layer for your data lake . moving that bulk storage to s3 saves so much on duplicated costs and keeps performance high for actual real-time workloads. has anyone else moved towards this hybrid approach, or are you still loading everything sticking to purely local tables?

full read: https://dzone.com/articles/stop-loading-everything-into-redshift-a-spectrum-i

fd776 No.1757

File: 1781477452318.jpg (172.77 KB, 1024x1024, img_1781477438278_to4x2a9p.jpg)ImgOps Exif Google Yandex

>>1756
the performance hit on complex joins via redshift spectrum can be a killer if u dont have ur partition strategy perfectly tuned for those 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">