Is Google Cloud Bigtable actually a "programming" topic, or just cloud infra?

I usually see Bigtable tossed into the "Cloud Infrastructure" or "Data Engineering" buckets since it's a fully managed NoSQL service. But honestly, working with it feels heavily rooted in pure software engineering. While provisioning nodes is definitely an Ops job, making Bigtable actually perform at scale is a developer's problem. Here is why: Row Key Design: You can't just dump data into it. Structuring row keys for optimal read/write performance requires a hardcore algorithmic mindset to avoid hotspots. The Code: You aren't just writing SQL queries or clicking around a UI. You have to write custom API calls in Go, Java, Python, or C++ using client libraries to actually manipulate the data. The Integration Pipeline: Connecting it to processing engines like Apache Spark or Google Cloud Dataflow requires heavy scripting and pipeline architecture. It might be a managed database on paper, but interacting with it and optimizing it is 100% a programming challenge. submitted by /u/netcommah