Platform Engineering

TCP #146: Most Streaming Pipelines Answer a Question Nobody Asked

Five questions and a simple break-even test for choosing streaming or micro-batch per pipeline.

Oct 18 • Amrut Patil

TCP #145: Athena Optimization, In the Order That Pays

Partition projection, Parquet economics, and the predicate mistakes that make partitioned tables scan in full.

Oct 11 • Amrut Patil

TCP #144: Three Queries That Find Your Athena Cost Problem

Athena bills by bytes scanned. The attribution data exists, but most teams never turn it into an optimization queue.

Oct 4 • Amrut Patil

TCP #142: ETL vs ELT Is Not a Platform-Wide Decision

Standardizing every pipeline on one pattern is how teams overpay for compute or create unnecessary latency.

Sep 20 • Amrut Patil

TCP #141: Seven Signals Your Organization Is Not Ready for Data Mesh

Decentralizing data ownership before the platform exists produces silos with better branding.

Sep 13 • Amrut Patil

TCP #140: How to Keep Your AWS Data Lake From Becoming a Data Swamp

A Terraform reference pattern for controlling schema, ownership, partitioning, permissions, and cost before your serverless data lake becomes untrusted.

Sep 6 • Amrut Patil

TCP #143: The Glue Job That Survives a Mid-Load Failure

Bookmarks, staging merges, late-arriving data, and recovery design for incremental S3-to-Redshift loads.

Sep 6 • Amrut Patil

TCP #133: Permission sets belong in a pipeline, not in the Identity Center console

The controls-as-code system for permission sets: repo structure, CI/CD deployment, privilege review gates, and drift detection

Jul 16 • Amrut Patil

TCP #132: Your Control Tower guardrails belong in Terraform, not the console

The controls-as-code system for preventive, detective, and proactive guardrails, with review, drift detection, and rollout order.

Jul 12 • Amrut Patil

TCP #131: The multi-account checklist regulated SaaS teams should have written

Account strategy, identity, networking, tenancy, and audit — each section with owners, cadences, and evidence.

Jul 9 • Amrut Patil

TCP #127: The ADR template that turns architecture into a written contract

Decision context, tradeoffs, risk, cost, compliance, and rollback captured in a format leadership can read.

Jun 21 • Amrut Patil

TCP# 124: The 6 golden paths worth building first, and how to sequence them.

Scored by frequency, friction, risk, and reach. With backlog template and adoption metrics.

May 24 • Amrut Patil

#nojs-banner { position: fixed; bottom: 0; left: 0; padding: 16px 16px 16px 32px; width: 100%; box-sizing: border-box; background: red; color: white; font-family: -apple-system, "Segoe UI", Roboto, Helvetica, Arial, sans-serif, "Apple Color Emoji", "Segoe UI Emoji", "Segoe UI Symbol"; font-size: 13px; line-height: 13px; } #nojs-banner a { color: inherit; text-decoration: underline; } This site requires JavaScript to run correctly. Please turn on JavaScript or unblock scripts