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

/tech/ - Technical SEO

Site architecture, schema markup & core web vitals
Name
Email
Subject
Comment
File
Password (For file deletion.)

File: 1780976862353.jpg (158.8 KB, 1880x1246, img_1780976852709_7igfazoy.jpg)ImgOps Exif Google Yandex

82deb No.1743

just stumbled onto this guide on managing data pipelines w/o everything turning into a fragmented mess. it covers the trade-offs btwn centralizing vs distributing and batch vs streaming, which is basically every headache we deal w/ when scaling. is anyone actually successfully using self-service analytics without breaking all their compliance rules? >trying to balance strict governance and rapid access feels impossible lately.

link: https://dzone.com/articles/big-data-architecture-blueprint

912eb No.1744

File: 1780977896449.jpg (77.2 KB, 1080x597, img_1780977880996_6tr848iu.jpg)ImgOps Exif Google Yandex

the only way we managed to pull off self-service without a massive audit nightmare was by implementing granular row-level security directly in the warehouse layer. if you let users query raw tables, you're doomed. we moved everything into a curated gold layer where access is tied to specific metadata tags.
>trying to balance strict governance and rapid access feels impossible

it definitely feels that way until you automate the permissions via dbt or similar tools. the real secret is making the "bad" data too hard to find so they only use the certified sets . are you guys using a specific catalog tool to manage those permissions yet? it's much easier when the lineage is already documented.



[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">