Urgent.News

What's breaking now, across hundreds of outlets.

Tech

Cloud costs were never a technology problem

I've been sharing what I see inside cloud accounts for months now Real accounts. Real numbers. Real messes and real fixes Here's what it all adds up to Cloud costs are not a technical problem The technology is fine. AWS and GCP are well-designed systems. The pricing is documented. The optimization tools exist. The knowledge is available The problem is human. It's the gap between the speed of…

Cloud costs are not a technical problem, but a human one. The technology behind cloud providers like AWS and GCP is well-designed, and the pricing is documented. Optimization tools and knowledge are readily available to the professionals. The issue lies in the gap between building new resources quickly and reviewing them thoroughly.

There is often a disconnect between the person who provisions a resource and the one who reviews the bill. This results in engineers being excellent at their jobs, but lacking a system for maintaining visibility over their built infrastructure. The remedy is simple: know what you're running, its cost, its purpose, and review it regularly, fixing what doesn't make sense and documenting decisions deliberately.

Teams that follow this practice consistently avoid crisis conversations, as they rarely find themselves scrambling to explain why infrastructure costs have tripled. Efficient infrastructure support allows teams to focus on building something worth the investment.

Rewritten by urgent.news; may contain errors — check the original.

Source: dev.to

Read the original at dev.to →

Report a problem with this story

More in Tech

Why Your Slow-Query Log Is Lying to You (a Little)

You've done the obvious work. You pulled a slow-query log off production, found the worst offenders, added indexes, rewrote a couple of queries, and shipped it. Response times improved.

  • Slow-query logs show queries over usual runtime but miss some cases
  • They don't capture rarely hit queries or cache state dependent problems
  • Enable SAVEQUERIES in WordPress for full query profiling during debugging

Why Your Full-Page Cache Needs an Opinion About Query Strings

Two different incidents on the same WordPress VIP-style multisite network, months apart, turned out to share one root cause.

  • Full-page cache key should not be determined by request contents.
  • Query strings often cause false cache misses due to tracking parameters.
  • Explicitly vary headers that genuinely affect response to prevent false caches.

Temporal.io vs Cadence vs AWS Step Functions: Distributed Workflow Orchestration & State Durability

Temporal.io vs Cadence vs AWS Step Functions: Distributed Workflow Orchestration & State Durability Executive Summary & Decision Matrix All three systems solve the same core problem — durable…

  • Temporal.io and Cadence share open-source codebase, Temporal forked Cadence in 2019
  • AWS Step Functions is managed, closed-source JSON interpreter relying on AWS durability
  • Temporal/Cadence outperform AWS Step Functions in sustained workflow throughput and lower latency

More from Sunday 22 November →