Home
Storia in 1 fonti
[Databricks on AWS #0] The Target Architecture: Isolating Prod, Dev, and Sandbox with Unity Catalog
The north-star design behind our Databricks platform — Lakehouse and Medallion under Unity Catalog governance, three fully isolated zones (prod, dev, sandbox), zero-copy reads, and a promote path that keeps humans out of production writes.
Raccontata da
dev.to
Timeline cronologica
- ·
[Databricks on AWS #0] The Target Architecture: Isolating Prod, Dev, and Sandbox with Unity Catalog
The north-star design behind our Databricks platform — Lakehouse and Medallion under Unity Catalog governance, three fully isolated zones (prod, dev, sandbox), zero-copy reads,…
- ·
[Databricks on AWS #2] RBAC on Databricks: Function-Role Groups, Workspace Assignment, and Why USER/ADMIN Isn't the Whole Story
Databricks RBAC done right: three account-level function-role groups, workspace USER/ADMIN assignment, and the mental split between what Databricks gives you built-in and the one…
- ·
[Databricks on AWS #3] Compute Governance on Databricks: Instance Pools, Cluster Policies, and Shared Clusters
Governing Databricks compute so nobody spins up a 128-core box at 2am: instance pools, cluster policies, an entitlement gate, and the apply-order gotcha — ending on a…
- ·
[Databricks on AWS #4] The BOOTSTRAP_TIMEOUT Mystery: Tracing a Databricks Cluster from Data Plane to Control Plane (Transit Gateway +…
Healthy EC2, perfect routing, and a Databricks cluster that still won't start. Tracing a BOOTSTRAP_TIMEOUT from the data plane to the control plane across a Transit Gateway and an…
- ·
[Databricks on AWS #5] Fixing Databricks BOOTSTRAP_TIMEOUT with AWS PrivateLink: Control Plane Over the Backbone, Zero New Subnets
Fixing a Databricks BOOTSTRAP_TIMEOUT with AWS PrivateLink — control-plane traffic over the AWS backbone with zero new subnets, zero new CIDR, and zero routing changes in an…