how do you handle the failover without doubling the latency on the second call?
November 7, 2026 at 9:42 AM
how do you handle the failover without doubling the latency on the second call?
Postgres on Railway now has:
• High availability with automatic failover
• Built-in connection pooling
• Backups and point-in-time recovery
• Auto image updates, CVE patching, and major version upgrades
• Agent skills & CLI support
blog.railway.com/p/managed-postgres
• High availability with automatic failover
• Built-in connection pooling
• Backups and point-in-time recovery
• Auto image updates, CVE patching, and major version upgrades
• Agent skills & CLI support
blog.railway.com/p/managed-postgres
November 5, 2026 at 8:02 PM
Postgres on Railway now has:
• High availability with automatic failover
• Built-in connection pooling
• Backups and point-in-time recovery
• Auto image updates, CVE patching, and major version upgrades
• Agent skills & CLI support
blog.railway.com/p/managed-postgres
• High availability with automatic failover
• Built-in connection pooling
• Backups and point-in-time recovery
• Auto image updates, CVE patching, and major version upgrades
• Agent skills & CLI support
blog.railway.com/p/managed-postgres
Failover cannot be an afterthought.
It is, fundamentally, how you create reliable databases in the face of inevitable server and network failures.
How we designed them in Neki ↓
It is, fundamentally, how you create reliable databases in the face of inevitable server and network failures.
How we designed them in Neki ↓
Designing a reliable unplanned failover — PlanetScale
How Neki detects a failed Postgres primary, and chooses a new one from the WAL that survived.
planetscale.com
November 5, 2026 at 5:46 PM
Failover cannot be an afterthought.
It is, fundamentally, how you create reliable databases in the face of inevitable server and network failures.
How we designed them in Neki ↓
It is, fundamentally, how you create reliable databases in the face of inevitable server and network failures.
How we designed them in Neki ↓
[Blog Archive] Veeam High Availability Cluster: #failover and automation - pt.2
Once the Veeam High Availability #Cluster has been created, there are two ways to perform the failover: manual and automated through Veeam ONE.
Manual failover does not require additional components to #veeamone
Once the Veeam High Availability #Cluster has been created, there are two ways to perform the failover: manual and automated through Veeam ONE.
Manual failover does not require additional components to #veeamone
Veeam High Availability Cluster: failover and automation - pt.2
nolabnoparty.com
November 7, 2026 at 12:46 PM
they insisted on
- strict serializability by default, no compromises
- horizontal scaling across nodes while maintaining the above
- seamless replication and repair with instant failover
- extremely stringent correctness testing
- strict serializability by default, no compromises
- horizontal scaling across nodes while maintaining the above
- seamless replication and repair with instant failover
- extremely stringent correctness testing
November 2, 2026 at 7:14 PM
they insisted on
- strict serializability by default, no compromises
- horizontal scaling across nodes while maintaining the above
- seamless replication and repair with instant failover
- extremely stringent correctness testing
- strict serializability by default, no compromises
- horizontal scaling across nodes while maintaining the above
- seamless replication and repair with instant failover
- extremely stringent correctness testing
Your WAN2 is plugged in. It has never been tested. pfsense health checks, routing and DNS failover sound simple until the night a carrier window kills your launch. https://www.valtersit.com/guides/networking/dual-wan-failover-because_my_internet_is_down_is_not_an_option/
Dual-WAN Failover: Because 'My Internet is Down' is Not an Option
www.valtersit.com
November 8, 2026 at 8:00 PM
Your WAN2 is plugged in. It has never been tested. pfsense health checks, routing and DNS failover sound simple until the night a carrier window kills your launch. https://www.valtersit.com/guides/networking/dual-wan-failover-because_my_internet_is_down_is_not_an_option/
Not found out how they replaced the R4 LW failover signal to Britain's nuclear deterrent.
November 9, 2026 at 7:00 PM
Not found out how they replaced the R4 LW failover signal to Britain's nuclear deterrent.
Failover billing verification: Confirm the backup service is active, paid and correctly sized. https://www.compuloop.com.au/telstra-outage-business-continuity-failover-lessons/?utm_source=bluesky&utm_medium=organic_social&utm_campaign=compuloop_oct_dec_2026&utm_content=d37
November 8, 2026 at 3:05 AM
Failover billing verification: Confirm the backup service is active, paid and correctly sized. https://www.compuloop.com.au/telstra-outage-business-continuity-failover-lessons/?utm_source=bluesky&utm_medium=organic_social&utm_campaign=compuloop_oct_dec_2026&utm_content=d37
[Blog Archive] Veeam High Availability Cluster: #failover and automation - pt.2
Once the Veeam High Availability #Cluster has been created, there are two ways to perform the failover: manual and automated through Veeam ONE.
Manual failover does not require additional components to #veeamone
Once the Veeam High Availability #Cluster has been created, there are two ways to perform the failover: manual and automated through Veeam ONE.
Manual failover does not require additional components to #veeamone
Veeam High Availability Cluster: failover and automation - pt.2
nolabnoparty.com
November 6, 2026 at 8:47 AM
Automated failover feels like the safe option. Sometimes it is the riskiest part of your setup.
DBA 3 covers backups and PITR, standby servers, streaming and logical replication, and the pitfalls of automated failover. Live online, 16 to 20 November.
shorturl.at/Ikedj
#PostgreSQL
DBA 3 covers backups and PITR, standby servers, streaming and logical replication, and the pitfalls of automated failover. Live online, 16 to 20 November.
shorturl.at/Ikedj
#PostgreSQL
November 9, 2026 at 12:02 PM
Automated failover feels like the safe option. Sometimes it is the riskiest part of your setup.
DBA 3 covers backups and PITR, standby servers, streaming and logical replication, and the pitfalls of automated failover. Live online, 16 to 20 November.
shorturl.at/Ikedj
#PostgreSQL
DBA 3 covers backups and PITR, standby servers, streaming and logical replication, and the pitfalls of automated failover. Live online, 16 to 20 November.
shorturl.at/Ikedj
#PostgreSQL
RPC Gateway and the engineering of failover
RPC Gateway shows a simple reliability pattern with real engineering depth: one endpoint in front of several RPC providers, with failover when one stops answering. The useful lesson is how to inspect timeout budgets, health states, retry policy, and respo
RPC Gateway shows a simple reliability pattern with real engineering depth: one endpoint in front of several RPC providers, with failover when one stops answering. The useful lesson is how to inspect timeout budgets, health states, retry policy, and respo
November 8, 2026 at 4:00 PM
RPC Gateway and the engineering of failover
RPC Gateway shows a simple reliability pattern with real engineering depth: one endpoint in front of several RPC providers, with failover when one stops answering. The useful lesson is how to inspect timeout budgets, health states, retry policy, and respo
RPC Gateway shows a simple reliability pattern with real engineering depth: one endpoint in front of several RPC providers, with failover when one stops answering. The useful lesson is how to inspect timeout budgets, health states, retry policy, and respo
Three picks from Learn Kubernetes Weekly 208:
• PostgreSQL failover safety
• Gateway API migration on EKS
• burn: compare cluster cost estimates with cloud bills
https://kube.today/issues/208
• PostgreSQL failover safety
• Gateway API migration on EKS
• burn: compare cluster cost estimates with cloud bills
https://kube.today/issues/208
November 4, 2026 at 11:46 AM
Three picks from Learn Kubernetes Weekly 208:
• PostgreSQL failover safety
• Gateway API migration on EKS
• burn: compare cluster cost estimates with cloud bills
https://kube.today/issues/208
• PostgreSQL failover safety
• Gateway API migration on EKS
• burn: compare cluster cost estimates with cloud bills
https://kube.today/issues/208
DNS failover closes the gap between DNS and reality: your authoritative nameserver can monitor targets and rewrite answers before users hit…
https://dev.to/_535eaafb7621edb176417e/dns-failover-explained-how-your-domain-survives-a-dead-server-5ef1
#networking #infrastructure
https://dev.to/_535eaafb7621edb176417e/dns-failover-explained-how-your-domain-survives-a-dead-server-5ef1
#networking #infrastructure
November 6, 2026 at 11:30 AM
DNS failover closes the gap between DNS and reality: your authoritative nameserver can monitor targets and rewrite answers before users hit…
https://dev.to/_535eaafb7621edb176417e/dns-failover-explained-how-your-domain-survives-a-dead-server-5ef1
#networking #infrastructure
https://dev.to/_535eaafb7621edb176417e/dns-failover-explained-how-your-domain-survives-a-dead-server-5ef1
#networking #infrastructure
yolorouter (⭐️ 290)
A self-hosted, OpenAI-compatible LLM gateway with multi-provider failover, key rotation, and a built-in admin console.
#go
A self-hosted, OpenAI-compatible LLM gateway with multi-provider failover, key rotation, and a built-in admin console.
#go
November 8, 2026 at 8:40 AM
yolorouter (⭐️ 290)
A self-hosted, OpenAI-compatible LLM gateway with multi-provider failover, key rotation, and a built-in admin console.
#go
A self-hosted, OpenAI-compatible LLM gateway with multi-provider failover, key rotation, and a built-in admin console.
#go
With managed planned failover for Amazon Aurora Global Database, you can failover to a secondary AWS Region while maintaining the replication topology and without having to recreate any secondary clusters.
Managed planned failovers with Amazon Aurora Global Database | Amazon Web Services
Amazon Aurora is a relational database service that combines the speed and availability of high-end commercial databases with the simplicity and cost effectiveness of open-source databases. Aurora has a distributed architecture that replicates a shared storage volume across three Availability Zones to provide a high availability solution with no data loss and failover time measured […]
aws.amazon.com
November 10, 2026 at 1:20 AM
With managed planned failover for Amazon Aurora Global Database, you can failover to a secondary AWS Region while maintaining the replication topology and without having to recreate any secondary clusters.
not 1 sqlite. LOTS of sqlites. one per account, plus a couple extra. it works remarkably well, it's just hard to have nice online failover.
November 2, 2026 at 1:44 PM
not 1 sqlite. LOTS of sqlites. one per account, plus a couple extra. it works remarkably well, it's just hard to have nice online failover.
AI ticket triage — before a mod reads a single word:
• Sentiment analysis
• Priority scoring
• Category detection
• AI-drafted reply suggestions
8 providers, automatic failover. Free.
https://cipher-dc.vercel.app
• Sentiment analysis
• Priority scoring
• Category detection
• AI-drafted reply suggestions
8 providers, automatic failover. Free.
https://cipher-dc.vercel.app
November 9, 2026 at 12:11 PM
AI ticket triage — before a mod reads a single word:
• Sentiment analysis
• Priority scoring
• Category detection
• AI-drafted reply suggestions
8 providers, automatic failover. Free.
https://cipher-dc.vercel.app
• Sentiment analysis
• Priority scoring
• Category detection
• AI-drafted reply suggestions
8 providers, automatic failover. Free.
https://cipher-dc.vercel.app
Self-Healing Cloud Networks: Autonomous Multi-Region Next-Hop ILB Failover with Google ADK, Terraform, and Cloud Run #devops #architecture
Self-Healing Cloud Networks: Autonomous Multi-Region Next-Hop ILB Failover with Google ADK, Terraform, and Cloud Run
Groups
Conversations
All groups and messages
Sign in
Self-Healing Cloud Networks: Autonomous Multi-Region Next-Hop ILB Failover with Google ADK, Terraform, and Cloud Run
0 views
Skip to first unread message
Eyal Estrin
unread,
7:39 AM (9 minutes ago)
to
https://medium.com/google-cloud/self-healing-cloud-networks-autonomous-multi-region-next-hop-ilb-failover-with-google-adk-806779de8b2b
Eyal Estrin
Author | Cloud Architect | AWS • Azure • GCP Insights
Social: @eyalestrin
Connect: https://linktr.ee/eyalestrin Blog: https://security-24-7.com
Reply all
Reply to author
Forward
dlvr.it
November 4, 2026 at 1:48 PM
Self-Healing Cloud Networks: Autonomous Multi-Region Next-Hop ILB Failover with Google ADK, Terraform, and Cloud Run #devops #architecture
Does stripping failed retry turns hurt failover quality, or do you pass a one-line error summary forward so the model still knows why the route died? Would guess most of that 18K is stack traces plus duplicated tool schemas in the retry calls.
November 6, 2026 at 9:20 PM
Does stripping failed retry turns hurt failover quality, or do you pass a one-line error summary forward so the model still knows why the route died? Would guess most of that 18K is stack traces plus duplicated tool schemas in the retry calls.
They also provide often types of databases and storage that not only back it up at a low level than you access it at but that automatically failover and switch seemlessly. For example Multi-AZ databases replicas and object storage.
November 5, 2026 at 4:17 AM
They also provide often types of databases and storage that not only back it up at a low level than you access it at but that automatically failover and switch seemlessly. For example Multi-AZ databases replicas and object storage.
ZFS covers HA via pvesr replication, but failover starts from the last synced snapshot — anything written since then is gone (min interval is 1 minute in the Proxmox docs). With a two-node 1U pair, plan a QDevice vote too; otherwise one dead node means no quorum and HA cannot recover.
November 7, 2026 at 12:55 PM
ZFS covers HA via pvesr replication, but failover starts from the last synced snapshot — anything written since then is gone (min interval is 1 minute in the Proxmox docs). With a two-node 1U pair, plan a QDevice vote too; otherwise one dead node means no quorum and HA cannot recover.
281 lines of Python that checks Redis Cluster slots, replica lag, and failover state, then alerts to Slack. For sysadmins running sharded Redis. #redis #python #infra https://www.valtersit.com/python/redis-cluster-health-checker/
Redis Cluster Health Checker
www.valtersit.com
November 5, 2026 at 3:00 PM
281 lines of Python that checks Redis Cluster slots, replica lag, and failover state, then alerts to Slack. For sysadmins running sharded Redis. #redis #python #infra https://www.valtersit.com/python/redis-cluster-health-checker/
No scale? No problem.
But off the top of my head I've run into: terrible concurrency w/per process connections, garbage and VACUUM overhead/performance, crappy heuristics query planner, WAL replication but DIY failover, no horizontal write scaling, write contention, jittery query latency, etc.
But off the top of my head I've run into: terrible concurrency w/per process connections, garbage and VACUUM overhead/performance, crappy heuristics query planner, WAL replication but DIY failover, no horizontal write scaling, write contention, jittery query latency, etc.
there is no reason to make a new database. postgres can do it. if you think postgres can't do it, you just haven't found the right way to enable it in pg_settings yet
November 2, 2026 at 7:39 PM
No scale? No problem.
But off the top of my head I've run into: terrible concurrency w/per process connections, garbage and VACUUM overhead/performance, crappy heuristics query planner, WAL replication but DIY failover, no horizontal write scaling, write contention, jittery query latency, etc.
But off the top of my head I've run into: terrible concurrency w/per process connections, garbage and VACUUM overhead/performance, crappy heuristics query planner, WAL replication but DIY failover, no horizontal write scaling, write contention, jittery query latency, etc.