# reliability Published articles for reliability. This is one page of public article previews, not the complete archive. Follow Next page to continue. Summaries are not the original full articles. ## How API Design Is Evolving for AI Agents, Security, Reliability, and Compliance DevFeed: [How API Design Is Evolving for AI Agents, Security, Reliability, and Compliance]() Original publisher: [Read original article]() Author: J Simpson Published: 2026-09-17T07:00:00Z Content type: article Language: en Sources: [Nordic APIs]() Topics: [API](), [Architecture & Design](), [Artificial Intelligence](), [reliability](), [Security]() Tags: [agents](), [ai-agents](), [api](), [api-architecture](), [api-as-a-product](), [api-design](), [api-discovery](), [api-security](), [architecture](), [authorization](), [blog](), [mcp](), [microservices](), [rate-limiting](), [reliability](), [security]() ### AI overview This article examines six ways API design is evolving as APIs serve AI agents and other machine consumers, with implications for security, reliability, and regulatory compliance. ### Source excerpt For over two decades, API design and architecture remained remarkably consistent. Perhaps it's the outsized influence of Roy Fielding's RESTful dissertation, but API designers have stuck to the principles of stateless architecture, resource-based endpoints, and HTTP commands to an impressive degree. That's all starting to change, now that we've radically recontextualized the way we use ... ## Worker Backpressure (Part 1) DevFeed: [Worker Backpressure (Part 1)]() Original publisher: [Read original article]() Author: Mikalai Barysau Published: 2026-09-17T00:00:00Z Content type: article Language: en Sources: [Canva Engineering]() Topics: [backpressure](), [Back end](), [reliability]() Tags: [backend](), [backpressure](), [dependencies](), [outage](), [queue](), [reliability](), [worker]() ### AI overview Canva describes Worker Backpressure, a reliability mechanism for queue workers that slows processing when dependencies fail and speeds it back up after recovery. During a cloud-provider outage, the mechanism helped prevent failed messages from accumulating on the Dead Letter Queue and avoided an on-call page. ### Source excerpt How we taught Canva's queue workers to slow down when dependencies fail, then speed back up on their own. ## AI Changed How Spotify Builds. What We Learned (and Fixed) About Quality at Higher Velocity DevFeed: [AI Changed How Spotify Builds. What We Learned (and Fixed) About Quality at Higher Velocity]() Original publisher: [Read original article]() Author: Spotify Engineering Published: 2026-09-16T19:13:53Z Content type: article Language: en Sources: [Spotify Engineering](), [Spotify Engineering Blog]() Topics: [Monitoring](), [reliability](), [Microservices](), [Data pipelines](), [Artificial Intelligence](), [Job]() Tags: [ai](), [bug](), [data-pipelines](), [jobs](), [microservices](), [monitoring](), [reliability]() ### AI overview Spotify describes how rapid change, content-processing weaknesses, capacity limits, and a scheduling bug contributed to delays in publishing episodes. It reports adding end-to-end monitoring, fixing the scheduler, lowering batch-job priority, and increasing capacity. ### Source excerpt Quality and reliability have always been a point of pride for Spotify. We run an extraordinarily complex... The post AI Changed How Spotify Builds. What We Learned (and Fixed) About Quality at Higher Velocity appeared first on Spotify Engineering. ## AI safety does not stop at the model DevFeed: [AI safety does not stop at the model]() Original publisher: [Read original article]() Author: Samar Abbas Published: 2026-09-15T00:00:00Z Content type: opinion Language: en Sources: [Temporal Blog]() Topics: [ai safety](), [Agent Harness](), [reliability](), [retry](), [Security]() Tags: [agent](), [agent-harness](), [ai](), [reliability](), [retry](), [safety](), [security](), [temporal-voices]() ### AI overview The article argues that AI safety extends beyond model behavior to the application layer, where companies must control agent authority and enforce approvals, policies, and credential limits. It emphasizes that these controls must remain reliable through crashes, timeouts, and retries, and presents Temporal Agent Harness as an execution-layer control point around an agent SDK. ### Source excerpt Auditing what an agent did is only half the job. Companies also have to control what agents may do, and make those limits hold when systems fail. ## A Backward NTP Clock Step Delayed a Python Scheduler's Measurements by Nine Days DevFeed: [A Backward NTP Clock Step Delayed a Python Scheduler's Measurements by Nine Days]() Original publisher: [Read original article]() Author: Philipp Lehmann (philipp.lehmann@gruppe.ai) Published: 2026-09-14T07:00:00Z Content type: tutorial Language: en Sources: [Philipp Lehmann]() Topics: [Python](), [Linux](), [systemd](), [Single Board Computer]() Tags: [embedded](), [linux](), [ntp](), [python](), [reliability](), [scheduler](), [single-board-computer](), [systemd](), [time](), [wall-clock-time]() ### AI overview A Python scheduler on an embedded Linux device silently stopped running after NTP corrected the system clock backward by about nine days. Because it used wall-clock time to measure elapsed time, the scheduler waited roughly nine days before running again. The article explains why a monotonic clock is the appropriate fix and mentions testing with an injected clock jump. ### Source excerpt time.time() vs time.monotonic() in a Python scheduler: a backwards NTP step delayed runs by nine days. Monotonic durations and a jump-injecting test. ## Temporal raises $550M at a $12.55B valuation as demand grows for reliable AI infrastructure DevFeed: [Temporal raises $550M at a $12.55B valuation as demand grows for reliable AI infrastructure]() Original publisher: [Read original article]() Author: Allanah Hughes Published: 2026-09-14T00:00:00Z Content type: release Language: en Sources: [Temporal Blog]() Topics: [AI Infrastructure](), [reliability](), [Orchestration](), [AI Platform]() Tags: [agents](), [ai](), [ai-infrastructure](), [announcements](), [funding](), [infrastructure](), [orchestration](), [outage](), [reliability](), [series](), [systems]() ### AI overview Temporal announces a $550 million Series E funding round at a $12.55 billion valuation. The company says the funding will support reliable infrastructure for long-running AI agents and applications, including orchestration and recovery across systems. ### Source excerpt AI is raising the bar for reliability. See why Temporal's $550M Series E, backed by Lightspeed and others, is built to meet that demand. ## A letter from Samar: a year of achievements, and what's next for us DevFeed: [A letter from Samar: a year of achievements, and what's next for us]() Original publisher: [Read original article]() Author: Samar Abbas Published: 2026-09-14T00:00:00Z Content type: opinion Language: en Sources: [Temporal Blog]() Topics: [reliability](), [Artificial Intelligence](), [OpenAI]() Tags: [agents](), [ai-agents](), [growth](), [openai](), [reliability](), [temporal](), [temporal-voices]() ### AI overview Temporal CEO Samar Abbas reviews a year of company growth, leadership changes, the Series E raise, platform usage, and customer examples. He argues that reliable infrastructure and Durable Execution remain important as AI increases application complexity and expectations. ### Source excerpt Temporal CEO Samar Abbas on a year of record growth, the Series E raise, and why Durable Execution is now core infrastructure for reliable AI agents. ## Every service needs an owner DevFeed: [Every service needs an owner]() Original publisher: [Read original article]() Author: Sridhar Rajarao Published: 2026-09-12T00:00:00Z Content type: article Language: en Sources: [Sridhar Rajarao]() Topics: [systems](), [incident]() Tags: [catalog](), [customer](), [incident](), [on-call](), [ownership](), [platform-engineering](), [production](), [reliability](), [service](), [service-catalog](), [sre](), [startups](), [team]() ### AI overview The article argues that growing organizations need a focused service catalog to make production ownership visible. It recommends recording each service's customer outcome, owning team, current on-call contact, deployment path, health dashboard, runbook, and dependencies, and maintaining those records as part of engineering work. ### Source excerpt A useful service catalog is not an inventory project. It is a public record of who owns a customer outcome when the system is healthy and when it fails. ## fsGroupChangePolicy: OnRootMismatch and the setgid Invariant That Makes It Sound DevFeed: [fsGroupChangePolicy: OnRootMismatch and the setgid Invariant That Makes It Sound]() Original publisher: [Read original article]() Author: Philipp Lehmann (philipp.lehmann@gruppe.ai) Published: 2026-09-11T07:00:00Z Content type: tutorial Language: en Sources: [Philipp Lehmann]() Topics: [container](), [mount](), [Security](), [Process]() Tags: [container](), [container-image](), [kubernetes](), [mount](), [network](), [performance](), [reliability](), [security](), [stateful](), [storage](), [waiting]() ### AI overview This article explains why a stateful pod can remain in ContainerCreating for fifteen minutes when fsGroup triggers a recursive chown across a large network-backed volume. It describes how fsGroupChangePolicy: OnRootMismatch can skip the recursive walk when the volume root group already matches, and discusses the setgid invariant that supports this behavior. ### Source excerpt Pod stuck in ContainerCreating from fsGroup recursive chown: fsGroupChangePolicy: OnRootMismatch, and why the setgid bit on the volume root makes it safe. ## Negative caching protects databases from repeated lookups for nonexistent keys DevFeed: [Negative caching protects databases from repeated lookups for nonexistent keys]() Original publisher: [Read original article]() Author: hello@ankit-rana.com Published: 2026-09-09T00:00:00Z Content type: tutorial Language: en Sources: [Ankit Rana | Mechanical Sympathy]() Topics: [Caching](), [Cache](), [Database](), [Security](), [Latency]() Tags: [cache](), [cache-penetration](), [caching](), [database](), [negative-caching](), [protection](), [redis](), [reliability](), [security](), [ttl]() ### AI overview Negative caching prevents repeated database queries for nonexistent keys by storing a distinguishable marker for negative results. The article explains how partner integrations, scrapers, stale clients, migrations, or attackers can exploit this gap and recommends using a shorter TTL for negative entries. ### Source excerpt A cache that stores only found values gives you no protection against lookups for things that do not exist, and a miss on a nonexistent key costs the full origin query every single time. If the key is user supplied, an attacker can generate unlimited unique misses and bypass the cache entirely, which is cache penetration. Caching the negative result fixes it, with a shorter TTL than positive entries because a value appearing is a much more likely event than one disappearing. ## kube-proxy in iptables Mode and Native nftables Rules in the Forward Chain DevFeed: [kube-proxy in iptables Mode and Native nftables Rules in the Forward Chain]() Original publisher: [Read original article]() Author: Philipp Lehmann (philipp.lehmann@gruppe.ai) Published: 2026-09-08T07:00:00Z Content type: article Language: en Sources: [Philipp Lehmann]() Topics: [proxy](), [Kernel](), [Virtual Private Network]() Tags: [firewall](), [handle](), [ip](), [kernel](), [kubernetes](), [linux](), [networking](), [proxy](), [reliability](), [vpn]() ### AI overview The article explains how native nftables rules added by a WireGuard-based mesh agent to the FORWARD chain can cause kube-proxy in iptables mode to abort synchronization silently, leaving service endpoints stale. It describes removing the conflicting rules by handle. ### Source excerpt kube-proxy iptables-nft sync silently aborts on native nftables rules a mesh agent adds to the FORWARD chain. Fix: nft delete rule by handle, ip and ip6. ## How Fixed Intervals Synchronize Distributed Clients and How Jitter Helps DevFeed: [How Fixed Intervals Synchronize Distributed Clients and How Jitter Helps]() Original publisher: [Read original article]() Author: hello@ankit-rana.com Published: 2026-09-07T00:00:00Z Content type: opinion Language: en Sources: [Ankit Rana | Mechanical Sympathy]() Topics: [reliability](), [distributed-systems](), [systems](), [Network](), [Cache](), [Redis]() Tags: [aws](), [cache](), [code](), [distributed-systems](), [jitter](), [network](), [reliability](), [resilience](), [retries](), [thundering-herd]() ### AI overview Fixed retry intervals, TTLs, restarts, reconnects, and other recurring events can cause independent clients in distributed systems to synchronize, producing repeated load spikes. Adding randomness, or jitter, helps break that alignment; the article cites AWS measurements indicating that full jitter improves total work and completion time under contention. ### Source excerpt Distributed systems synchronise themselves without being told to: every client that retries on a fixed interval, restarts after a deploy, or reconnects after a network blip ends up firing at the same moment as every other client. The resulting spike is a self-inflicted denial of service that no single component is responsible for. Adding randomness to any repeating interval breaks the alignment, and it is usually one line of code against a failure mode that otherwise requires capacity you never needed. ## Cache stampede: how one expired key takes down the database DevFeed: [Cache stampede: how one expired key takes down the database]() Original publisher: [Read original article]() Author: hello@ankit-rana.com Published: 2026-09-05T00:00:00Z Content type: tutorial Language: en Sources: [Ankit Rana | Mechanical Sympathy]() Topics: [Cache](), [Caching](), [Database](), [consistent hashing](), [Redis]() Tags: [cache-stampede](), [caching](), [connection-pool](), [consistent-hashing](), [distributed-systems](), [jitter](), [query](), [redis](), [reliability](), [thundering-herd](), [traffic](), [ttl]() ### AI overview This article explains how a cache stampede occurs when a hot key expires and many requests simultaneously recompute the same value against the database. It recommends TTL jitter to prevent synchronized expirations and request coalescing so only one caller recomputes while others wait or serve stale data. It also discusses cache warming and consistent hashing for broader cache-failure scenarios. ### Source excerpt A cache TTL is a scheduled simultaneous failure: every request being served from one key misses at the same instant and goes to the origin together. If the recompute takes two seconds, every request arriving during those two seconds also misses, so the pileup grows faster than it drains. Jitter on the TTL stops keys expiring in lockstep, and request coalescing so only one caller recomputes while the rest wait or serve stale is what stops a single expensive key from saturating the database. ## AI data centers: the five hard problems money cannot buy away DevFeed: [AI data centers: the five hard problems money cannot buy away]() Original publisher: [Read original article]() Author: Sridhar Rajarao Published: 2026-08-30T00:00:00Z Content type: article Language: en Sources: [Sridhar Rajarao]() Topics: [Artificial Intelligence](), [data centers](), [Hardware](), [systems]() Tags: [ai](), [capacity](), [compute](), [data-centers](), [datacenters](), [hardware](), [heat](), [infrastructure](), [power](), [reliability]() ### AI overview The article argues that AI data-center expansion is constrained by the simultaneous need to secure power, grid connections, cooling and water strategies, equipment, skilled workers, permits, and productive compute. It discusses five industry challenges, with the supplied text covering power constraints and the physical and water implications of liquid cooling. ### Source excerpt The AI buildout is not mainly a real-estate problem. It is a race to integrate power, cooling, equipment, permits, and useful compute at the same time. ## Why Senior Leaders Should Attend Post-Incident Reviews for Major Cloud Incidents DevFeed: [Why Senior Leaders Should Attend Post-Incident Reviews for Major Cloud Incidents]() Original publisher: [Read original article]() Author: Sridhar Rajarao Published: 2026-08-29T00:00:00Z Content type: opinion Language: en Sources: [Sridhar Rajarao]() Topics: [incident](), [Cloud](), [control-plane](), [Deployment]() Tags: [cloud](), [control-plane](), [customers](), [deploy](), [incident](), [incident-management](), [leadership](), [major](), [operations](), [post](), [postmortems](), [reliability](), [review](), [service]() ### AI overview The article argues that senior leaders should attend Post Incident Reviews for major cloud incidents because failures can affect many customers and teams. Leadership helps approve cross-team changes, resolve trade-offs, and ensure corrective actions are completed. ### Source excerpt For major incidents, a Post Incident Review is not an operations meeting. It is where leaders remove the blockers that keep the service from becoming safer. ## Why GitHub feels less reliable lately DevFeed: [Why GitHub feels less reliable lately]() Original publisher: [Read original article]() Author: Sridhar Rajarao Published: 2026-08-23T00:00:00Z Content type: opinion Language: en Sources: [Sridhar Rajarao]() Topics: [GitHub](), [incident](), [migration](), [systems](), [Azure](), [GitHub Actions](), [pull-requests]() Tags: [autoscaling](), [capacity](), [concurrency](), [data-centers](), [deployment](), [github](), [incident](), [incident-management](), [istio](), [reliability](), [request](), [resilience](), [sre](), [transformation]() ### AI overview The article argues that GitHub's recent reliability problems reflect the difficult middle of a major infrastructure transformation. It connects incidents to migration complexity, unsafe automation, configuration mistakes, capacity and concurrency weaknesses, database migration errors, and autoscaling problems. ### Source excerpt GitHub is not having one outage problem. Its recent incident reports show the difficult middle of a platform transformation. ## How MongoDB Atlas and Temporal support reliable production RAG and AI agents DevFeed: [How MongoDB Atlas and Temporal support reliable production RAG and AI agents]() Original publisher: [Read original article]() Author: Suresh Ramappa Published: 2026-08-13T00:00:00Z Content type: opinion Language: en Sources: [Temporal Blog]() Topics: [MongoDB](), [Retrieval Augmented Generation (RAG)](), [AI Infrastructure](), [Artificial Intelligence](), [reliability]() Tags: [agentic](), [agents](), [ai](), [ai-infrastructure](), [api](), [data](), [embeddings](), [long-running](), [mongodb](), [outages](), [pipelines](), [production](), [rag](), [recovery](), [reliability](), [retries](), [retrieval](), [temporal-voices]() ### AI overview The article argues that MongoDB Atlas and Temporal address different reliability needs in production RAG and AI agent systems. Atlas provides operational data, embeddings, vector search, and agent memory in one platform, while Temporal provides durable execution for crash recovery, retries, and long-running ingestion and agent workflows. ### Source excerpt Why MongoDB Atlas and Temporal are better together for AI: one data platform, one durable execution layer, for RAG and agents in prod. ## Using observability to verify TLS certificate rotation in production DevFeed: [Using observability to verify TLS certificate rotation in production]() Original publisher: [Read original article]() Author: Sridhar Rajarao Published: 2026-08-13T00:00:00Z Content type: article Language: en Sources: [Sridhar Rajarao]() Topics: [TLS (Transport Layer Security)](), [observability](), [TLS handshake](), [Automation](), [nginx](), [Kubernetes]() Tags: [automation](), [nginx](), [observability](), [reliability](), [sre](), [tls](), [tls-handshake]() ### AI overview The article explains that automating certificate renewal does not prove that production endpoints serve the new certificate. It recommends externally probing customer-facing endpoints and measuring certificate details and real TLS handshakes across proxies, regions, ingress controllers, CDNs, gateways, and other endpoints. ### Source excerpt Automation renews a certificate. Observability proves every endpoint is serving it and customers can complete a TLS handshake. ## The Pulse: Quitting Spotify Podcasts over reliability DevFeed: [The Pulse: Quitting Spotify Podcasts over reliability]() Original publisher: [Read original article]() Author: Ivan Klaric Published: 2026-07-30T15:51:38Z Content type: opinion Language: en Sources: [The Pragmatic Engineer]() Topics: [Spotify](), [reliability](), [Streaming](), [RSS Feed]() Tags: [article](), [reliability](), [rss](), [streaming]() ### AI overview The author stopped publishing video podcast episodes on Spotify after encountering repeated reliability problems processing video episodes. Audio episodes remain available through Spotify's RSS feed, while video episodes are published on YouTube. ### Source excerpt Spotify's podcast platform has become chronically unreliable since the company's leadership started boasting about AI adoption. Competitors haven't had similar issues, so I offboarded from Spotify. ## ITIL vs SRE: why the big clouds went their own way DevFeed: [ITIL vs SRE: why the big clouds went their own way]() Original publisher: [Read original article]() Author: Sridhar Rajarao Published: 2026-07-26T00:00:00Z Content type: opinion Language: en Sources: [Sridhar Rajarao]() Topics: [SRE](), [site-reliability-engineering](), [Development](), [Terraform](), [pulumi](), [Availability](), [feature flags](), [incident]() Tags: [automated](), [aws](), [azure](), [cloud](), [feature-flags](), [gcp](), [human-review](), [hyperscaler](), [incident](), [incident-management](), [infrastructure-as-code](), [itil](), [on-call](), [postmortems](), [pulumi](), [release](), [reliability](), [service-catalog](), [sre](), [terraform]() ### AI overview This opinion article compares ITIL practices with SRE operations at hyperscaler scale. It argues that human change boards, single production instances, developer-to-operations handoffs, documentation-first configuration management, and weekly release windows do not fit environments serving millions of external customers. It describes automated approvals, gradual deployments, service-team ownership, infrastructure as code, continuous release, error budgets, SLOs, and blameless postmortems as alternatives. ### Source excerpt The big clouds don't run ITIL. Five assumptions ITIL makes that break at hyperscaler scale, and what AWS, Azure, GCP, and OCI use instead. ## Control Reliability Engineering (CRE): Applying SRE Principles to Cybersecurity Controls DevFeed: [Control Reliability Engineering (CRE): Applying SRE Principles to Cybersecurity Controls]() Original publisher: [Read original article]() Author: phil7672 Published: 2026-07-25T05:52:21Z Content type: article Language: en Sources: [Risk and Cyber]() Topics: [Cybersecurity](), [SRE](), [Monitoring](), [reliability](), [plotting]() Tags: [benchmarking](), [cybersecurity](), [leadership](), [monitoring](), [reliability](), [reliability-engineering](), [risk](), [sre](), [technology]() ### AI overview This article applies SRE principles to cybersecurity controls, arguing that control effectiveness matters more than input-focused budget comparisons. It highlights continuous control monitoring to detect controls that are broken, misconfigured, or incomplete when needed. ### Source excerpt Security breaches are often not the result of awesome attacker capabilities or the sudden emergence of sophisticated zero-day exploits. Instead, what we usually find are the controls designed to stop the attack were believed to be operational but were actually broken or misconfigured at the moment when they were needed. Sometimes they were never fully in place to meet the security team's original intent. So, continuous control monitoring is needed to counter the natural decay that occurs to... ## Session revocations at scale DevFeed: [Session revocations at scale]() Original publisher: [Read original article]() Author: Llew Vallis Published: 2026-07-22T00:00:01Z Content type: article Language: en Sources: [Canva Engineering]() Topics: [sessions](), [Cookies](), [Authorization](), [Caching](), [MySQL](), [scaling](), [gateway](), [Redis](), [reliability]() Tags: [backend](), [caching](), [cookies](), [gateway](), [mysql](), [permissions](), [redis](), [reliability](), [scaling](), [security](), [sessions]() ### AI overview Canva describes how it manages session revocations for hundreds of millions of users. The system keeps revocations in memory for fast gateway checks, while MySQL handles refresh-time lookups; the article explains how loading the cache during deployments created database load and discusses evaluating Redis as a caching solution. ### Source excerpt How Canva keeps hundreds of millions of user sessions fast and secure ## Why Temporal is the front-of-shirt sponsor for Crystal Palace DevFeed: [Why Temporal is the front-of-shirt sponsor for Crystal Palace]() Original publisher: [Read original article]() Author: Samar Abbas Published: 2026-07-17T00:00:00Z Content type: opinion Language: en Sources: [Temporal Blog]() Topics: [Software](), [reliability](), [Job](), [OpenAI]() Tags: [announcements](), [communities](), [company](), [developer](), [enterprise-technology](), [reliability](), [software](), [sponsor]() ### AI overview Temporal explains its front-of-shirt sponsorship of Crystal Palace by comparing the club's supporter loyalty with Temporal's focus on reliable software workflows. The article also mentions Temporal's reported $300 million Series D and $5 billion valuation. ### Source excerpt Temporal and Crystal Palace are teaming up, uniting fan and developer communities built on a loyalty that's earned, not manufactured. ## Introducing Temporal's new Build, Operate, and Secure org, led by Preeti Somal DevFeed: [Introducing Temporal's new Build, Operate, and Secure org, led by Preeti Somal]() Original publisher: [Read original article]() Author: Preeti Somal Published: 2026-07-10T00:00:00Z Content type: release Language: en Sources: [Temporal Blog]() Topics: [Development](), [Software Engineering](), [distributed-systems]() Tags: [announcements](), [engineering](), [organization](), [reliability](), [software-development]() ### AI overview Temporal announces a new Build, Operate, and Secure organization led by Preeti Somal as EVP. The organization brings Engineering, Product, and Design together under one charter to build, operate, and secure the company's products, with goals including faster iteration, a more consistent product experience, and continued reliability. ### Source excerpt Temporal announces a new Build, Operate, and, Secure org led by EVP Preeti Somal, uniting Engineering, Product, and Design under one charter. [Next page]()