Cybersecurity
Bulk Data Sharing Design
Design bulk file and lake export as a B2B product surface - the two-camp choice between Parquet file-drops on object storage and native warehouse/lake sharing (Snowflake shares, Delta Sharing, linked datasets), the partitioning and schema-evolution contract across batches, delivery cadence and freshness commitments (full dump vs incremental vs CDC vs streaming), shared-bucket security with per-recipient credentials, egress cost allocation, and cross-border data residency. Use whenever the user mentions bulk export, data dumps to S3, Parquet, Snowflake shares, Delta Sharing, or export freshness SLAs - even if they never say "bulk data sharing". Do NOT use for live SQL endpoints - use samber/developer-platform-skills@sql-jdbc-access-design instead.
- Publisher / source
- samber/developer-platform-skills (found on skills.sh)
- Upstream record
- samber/developer-platform-skills
- Version
- Version 2
- Published
- Publication review
- Approved for publication
- Content fingerprint
54554d6ffb6f1f86cca71e91b4b412af943021195618515523d9844a58f81258