# resiliency Published articles for resiliency. 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 Intuit and AWS systematically improved resiliency on ElastiCache using AWS Fault Injection Service DevFeed: [How Intuit and AWS systematically improved resiliency on ElastiCache using AWS Fault Injection Service]() Original publisher: [Read original article]() Author: Ryan Sheahan Published: 2026-09-17T15:59:44Z Content type: article Language: en Sources: [AWS Database Blog]() Topics: [Amazon ElastiCache](), [AWS Fault Injection Service (FIS)](), [Resilience](), [Caching](), [reliability](), [Availability]() Tags: [advanced-300](), [amazon-elasticache](), [applications](), [architecture](), [availability](), [aws](), [aws-fault-injection-service-fis](), [caching](), [clusters](), [customer-experience](), [customer-solutions](), [monitoring](), [recovery](), [resilience](), [resiliency]() ### AI overview AWS and Intuit describe validating Amazon ElastiCache resilience during an Availability Zone impairment with AWS Fault Injection Service. The post covers experiment setup, measurements, configuration issues, and reported recovery improvements under production-level load. ### Source excerpt Learn how Intuit and AWS validated Amazon ElastiCache resilience under a real Availability Zone impairment using AWS Fault Injection Service, cutting recovery from over 50 minutes to under 2 minutes with no manual intervention and reducing customer impact to effectively zero. ## Fault tolerant distributed training on Amazon EKS using NVRx DevFeed: [Fault tolerant distributed training on Amazon EKS using NVRx]() Original publisher: [Read original article]() Author: Aravind Neelakantan Published: 2026-09-16T18:59:25Z Content type: tutorial Language: en Sources: [Artificial Intelligence]() Topics: [NCCL](), [Amazon Elastic Kubernetes Service](), [PyTorch](), [distributed-training](), [Resilience](), [GPU]() Tags: [advanced-300](), [amazon-eks](), [amazon-elastic-kubernetes-service](), [async](), [benchmarks](), [distributed-training](), [gpu](), [pytorch](), [resiliency](), [technical-how-to]() ### AI overview This tutorial integrates NVIDIA Resiliency Extension (NVRx) with PyTorch FSDP training on Amazon EKS. It covers asynchronous checkpointing, in-process restart, and in-job restart, and reports H100 benchmarks at 2- to 8-node scale with 99%+ training efficiency and recovery measured in seconds. ### Source excerpt Integrate NVIDIA Resiliency Extension (NVRx) into PyTorch FSDP training on Amazon EKS to overlap checkpoint I/O with training and recover from GPU faults in seconds. This post covers async checkpointing, in-process restart, and ft_launcher in-job restart, with H100 benchmarks at 2 to 8 nodes showing 99%+ training efficiency and second-scale recovery. ## How NVIDIA NVLink 6 Delivers Multi-Layer Resiliency for AI Factories DevFeed: [How NVIDIA NVLink 6 Delivers Multi-Layer Resiliency for AI Factories]() Original publisher: [Read original article]() Author: Elizabeth Goodman Published: 2026-09-15T16:55:00Z Content type: article Language: en Sources: [NVIDIA Developer](), [NVIDIA Technical Blog]() Topics: [NVLink](), [Nvidia](), [AI Factory](), [AI Infrastructure](), [Hardware]() Tags: [agentic-ai-generative-ai](), [ai](), [ai-factory](), [ai-infrastructure](), [data-center-cloud](), [hardware](), [industry](), [networking](), [networking-communications](), [nvidia](), [nvlink](), [resiliency](), [vera-rubin]() ### AI overview The article describes how NVIDIA NVLink 6 supports resiliency in large-scale AI factories. It explains that Vera Rubin NVL72 connects 72 Rubin GPUs into a single scale-up domain and outlines a multilayer approach using lossless networking, error correction, retry, flow control, and error containment to support continuous training and inference operations. ### Source excerpt For operators of large-scale AI factories, maximizing continuous output is essential for productivity. In massive-scale AI training, every GPU in the cluster... ## How to Deal With Errors and Failures in LLM-Powered Applications DevFeed: [How to Deal With Errors and Failures in LLM-Powered Applications]() Original publisher: [Read original article]() Author: ByteByteGo Published: 2026-09-07T15:31:35Z Content type: tutorial Language: en Sources: [ByteByteGo]() Topics: [Large Language Model](), [App](), [Language models]() Tags: [applications](), [concurrency-control](), [errors](), [how-to](), [llm](), [rate-limiting](), [resiliency](), [retry]() ### AI overview A tutorial on error handling and resiliency for LLM-powered applications. It covers failures such as unavailable networks, rejected requests, invalid JSON, hallucinations, slow responses, timeouts, retries, fallbacks, circuit breakers, rate limiting, queues, concurrency control, safe tool calls, and response streaming. ### Source excerpt Apart from normal processing, the application also sends data to a large language model (LLM). It then uses the model's response to carry out a task. ## Roadmap decisions rather than dates. DevFeed: [Roadmap decisions rather than dates.]() Original publisher: [Read original article]() Published: 2026-08-11T14:00:00Z Content type: opinion Language: en Sources: [Will Larson - Irrational Exuberance]() Topics: [Development](), [Passkeys](), [resiliency](), [User Experience](), [Mobile](), [Web]() Tags: [development](), [experience](), [implementation](), [mobile](), [phishing](), [resiliency](), [web]() ### AI overview The article argues that product roadmaps should prioritize decisions and execution constraints rather than fixed dates. It uses the development and rollout of passkey support at Imprint as an example, describing implementation behind a feature flag, staged web release, feedback iteration, and expansion to native mobile experiences. ### Source excerpt One thing that bothered me about Imprint's product after joining was our lack of passkey support. Passkey support is a rare opportunity to increase resiliency to phishing attacks while simultaneously reducing login friction. If it's good for our members, our partners, and our product, it felt like something we should have already shipped. Nonetheless, it was hard to get it onto the roadmap alongside everything else we were working on. To dig into passkeys, I started sketching out the implementation as a side quest. Some iterations later, I had something implemented behind a disabled feature flag for team review. At that point, most problems had a concrete solution implemented, and the remaining issues were messy intersections between passkey implementation and user experience. Issues remained, but the tangible implementation made tradeoffs explicit, and we were able to work through them. Soon thereafter, we launched passkeys to a small group in our web experience, iterated on feedback, finalized the details, and brought those details forward to our native mobile experiences as well. It never got onto the roadmap, but it did ship. Our passkey release planted a seed for me, but it required another experience to fully germinate. We had a discussion about hitting a date for a product extension we're developing. Our conversation kept anchoring on the idea that pulling in a date was dependent on pushing out dates for other projects. Presenting two conflicting projects as requiring timeline tradeoffs wouldn't have caused me to blink an eye five years ago, but in this conversation it inspired a sort of instinctual revolt: with modern development techniques, I believe very few projects are essentially constrained by execution bandwidth. Some are constrained by approvals, others are constrained by cross-team and cross-functional handoffs, and many are constrained by missing decisions, but almost none should be constrained purely on time. Shifting blocks of time across project ## Top Resiliency Patterns for Developers DevFeed: [Top Resiliency Patterns for Developers]() Original publisher: [Read original article]() Author: Saurabh Dashora Published: 2026-04-21T06:08:56Z Content type: tutorial Language: en Sources: [System Design Codex]() Topics: [resiliency](), [distributed-systems](), [circuit](), [Availability](), [Latency](), [Scalability](), [Architecture & Design]() Tags: [availability](), [circuit](), [distributed-systems](), [latency](), [monitoring](), [resiliency](), [scalability](), [timeout]() ### AI overview A quick guide to resiliency patterns for distributed systems. It introduces downstream and upstream patterns, then explains timeouts, circuit breakers, and retries with exponential backoff as ways to limit cascading failures and help downstream services recover. ### Source excerpt Quick Guide ## What is the BFF Pattern? DevFeed: [What is the BFF Pattern?]() Original publisher: [Read original article]() Author: Saurabh Dashora Published: 2026-04-07T08:41:56Z Content type: tutorial Language: en Sources: [System Design Codex]() Topics: [BFF](), [Amazon API Gateway](), [backends](), [client](), [interface](), [resiliency](), [Orchestration](), [rate-limiting]() Tags: [api-gateway](), [authentication](), [backends](), [bff](), [cache-control](), [client](), [decoupling](), [mobile](), [rate-limiting](), [resiliency]() ### AI overview The article explains the Backends-for-Frontends (BFF) pattern, in which dedicated API gateways serve different client types such as web browsers, mobile apps, and public or partner APIs. It describes how BFFs tailor APIs, isolate client-specific logic, and support functions including rate limiting, authentication, header sanitization, and cache control. It also discusses benefits such as resiliency, client-specific optimization, and faster development, along with drawbacks including code duplication and increasing complexity. ### Source excerpt And when do you need it? ## 2026 Research: The Top AI Infrastructure Risks and Identity Gaps DevFeed: [2026 Research: The Top AI Infrastructure Risks and Identity Gaps]() Original publisher: [Read original article]() Author: jack.pitts@goteleport.com (Jack Pitts) Published: 2026-02-17T00:00:00Z Content type: article Language: en Sources: [Teleport]() Topics: [AI Infrastructure](), [deploying agentic AI](), [Security](), [incident](), [AI Strategy]() Tags: [2026](), [agentic-ai](), [ai](), [ai-infrastructure](), [report](), [resiliency](), [security](), [survey]() ### AI overview New Teleport research examines AI infrastructure security risks, adoption trends, and identity gaps. It reports that agentic AI adoption is advancing faster than security preparedness and identifies confidently wrong configurations as a leading concern. ### Source excerpt New Teleport research examines rising AI infrastructure security risks, adoption trends, and the identity controls reducing incident rates in 2026 and beyond. ## Building production-ready generative AI: How Temporal supercharges Google's Gemini and Veo DevFeed: [Building production-ready generative AI: How Temporal supercharges Google's Gemini and Veo]() Original publisher: [Read original article]() Author: Ka Wo Fong Published: 2025-07-17T00:00:00Z Content type: tutorial Language: en Sources: [Temporal Blog]() Topics: [Artificial Intelligence](), [Generative AI](), [distributed-systems](), [API](), [Cloud]() Tags: [agentic-ai](), [ai](), [ai-agents](), [api](), [architecture](), [distributed-systems](), [generative-ai](), [google-cloud](), [how-to](), [reliability](), [resiliency]() ### AI overview This tutorial explains the engineering challenges of making long-running, stateful generative AI workflows reliable in production. It uses an open-source video generation system with Gemini 2.5 Flash, Veo 2, and Google Cloud Storage to demonstrate how Temporal's Durable Execution platform can provide resiliency and reliability. ### Source excerpt Learn how to navigate the pitfalls of producing agentic AI for prod with Temporal and Google's Gemini and Veo. ## FAANG and Startup Engineering: How Scale, Delivery Processes, and Compensation Differ DevFeed: [FAANG and Startup Engineering: How Scale, Delivery Processes, and Compensation Differ]() Original publisher: [Read original article]() Published: 2025-05-19T00:00:00Z Content type: opinion Language: en Sources: [Gaurav Sarma's Blog]() Topics: [distributed-systems](), [CI/CD](), [SIEM, Security, Observability](), [resiliency](), [systems]() Tags: [career](), [ci-cd](), [distributed-systems](), [early-stage](), [experience](), [faang](), [metrics](), [monitor](), [process](), [resiliency](), [startups]() ### AI overview The author argues that experience at large technology companies can expose engineers to scalable distributed systems, standardized release practices, CI/CD, monitoring, and metrics. The article contrasts these processes with the faster delivery of early-stage startups, which may introduce more process as bugs and resiliency issues grow, and discusses compensation and equity differences. ### Source excerpt I have worked in early stage, late stage startups and bigger companies as well. "FAANG in your 20s often makes your skills deteriorate"... ## How Teleport Simplifies Just-in-Time Access DevFeed: [How Teleport Simplifies Just-in-Time Access]() Original publisher: [Read original article]() Author: jack@goteleport.com (Jack Pitts) Published: 2025-04-23T00:00:00Z Content type: tutorial Language: en Sources: [Teleport]() Topics: [JIT](), [Access Control](), [resiliency](), [API](), [Single sign-on (SSO)](), [Command-line interface]() Tags: [access-control](), [api](), [authorization](), [cli](), [condition](), [jit](), [least-privilege](), [policy](), [regex](), [resiliency](), [sso]() ### AI overview This article explains how Teleport integrates just-in-time access with identity, policy, and workflows. It describes role-based access controls, request restrictions, automated approvals, and requirements such as reasons, approval thresholds, regex validation, session moderation, and dual authorization. ### Source excerpt Just-in-time access isn't always easy. Explore how Teleport tackles JIT challenges by simplifying least privilege, streamlining requests, and strengthening resiliency. ## The Missing Link Between Infrastructure Resiliency and High-Velocity Engineering DevFeed: [The Missing Link Between Infrastructure Resiliency and High-Velocity Engineering]() Original publisher: [Read original article]() Author: info@goteleport.com (Jack Pitts) Published: 2025-04-10T00:00:00Z Content type: opinion Language: en Sources: [Teleport]() Topics: [resiliency](), [Security](), [API keys](), [Cloud](), [Social engineering](), [Microservices](), [systems](), [Kubernetes clusters]() Tags: [api-keys](), [cloud-services](), [kubernetes-clusters](), [microservices](), [resiliency](), [security](), [social-engineering](), [systems]() ### AI overview Teleport CEO Ev Kontsevoy and analyst Jack Poller argue that modern infrastructure resiliency depends on rethinking identity and access. The article links credential-based identity attacks and exposed API keys with the growing complexity of hybrid and multi-cloud systems, microservices, Kubernetes clusters, ephemeral workloads, and machine identities. ### Source excerpt Teleport CEO Ev Kontsevoy and analyst Jack Poller explore why traditional identity approaches fail--and how Infrastructure Identity unlocks resiliency. ## Temporal Nexus is now generally available DevFeed: [Temporal Nexus is now generally available]() Original publisher: [Read original article]() Author: Phil Prasek Published: 2025-03-06T00:00:00Z Content type: release Language: en Sources: [Temporal Blog]() Topics: [Programming](), [Architecture & Design](), [resiliency](), [Security](), [observability](), [SDKs](), [Go Language](), [Java](), [Cloud]() Tags: [announce](), [connectivity](), [go](), [java](), [migration](), [netflix](), [network](), [observability](), [product-news](), [resiliency](), [reverse-proxy](), [sdk](), [security]() ### AI overview Temporal announces the general availability of Temporal Nexus, a feature for connecting Temporal Applications across isolated Namespaces. It provides service contracts for cross-namespace Workflow calls, with support for observability, debugging, security, fault isolation, and multi-region connectivity in Temporal Cloud. ### Source excerpt Temporal Nexus is now generally available! Nexus allows you to connect your Temporal Applications across isolated Namespaces. ## Announcing Nexus: Connect Temporal Applications across isolated Namespaces DevFeed: [Announcing Nexus: Connect Temporal Applications across isolated Namespaces]() Original publisher: [Read original article]() Author: Roey Berman Published: 2024-12-20T08:00:00Z Content type: release Language: en Sources: [Temporal Blog]() Topics: [distributed-systems](), [observability](), [Security](), [reliability](), [Architecture & Design]() Tags: [architecture](), [distributed-systems](), [observability](), [product-news](), [reliability](), [resiliency](), [security]() ### AI overview Temporal announces Nexus, a built-in Temporal Platform feature that connects applications and workflows across isolated Namespaces. The Public Preview combines durable execution, queue-based Workers, security, observability, debugging, and fault isolation for cross-team and cross-domain communication. ### Source excerpt Discover Temporal Nexus, a built-in platform feature connecting workflows across namespaces with durable execution, security, and integrated observability. ## Top 10 Launches of Launch Week 13 DevFeed: [Top 10 Launches of Launch Week 13]() Original publisher: [Read original article]() Author: Paul Copplestone Published: 2024-12-06T07:00:00Z Content type: release Language: en Sources: [Supabase Blog]() Topics: [Supabase](), [Database](), [WebSocket](), [GitHub Actions](), [Artificial Intelligence]() Tags: [features](), [github-actions](), [launch](), [queue](), [realtime](), [resiliency](), [scalability]() ### AI overview Supabase highlights the top 10 launches from Launch Week 13, including Supabase Cron, an upgraded AI Assistant, Edge Functions features, CLI v2 configuration as code, high-performance disks, project restoration from backups, database.build updates, Oriole Beta7, Supabase Queues, and a coordinated launch with other developer tools. ### Source excerpt Highlights from Launch Week 13 ## Durable RAG with Temporal and Chainlit DevFeed: [Durable RAG with Temporal and Chainlit]() Original publisher: [Read original article]() Author: Sergey Ustimenko Published: 2024-09-14T09:00:00Z Content type: tutorial Language: en Sources: [Temporal Blog]() Topics: [Retrieval Augmented Generation (RAG)](), [Orchestration](), [Conversational AI](), [reliability](), [resiliency](), [Framework](), [Scalability](), [Open Source]() Tags: [agents](), [ai](), [applications](), [business](), [business-intelligence](), [how-to](), [rag](), [resiliency](), [workflows]() ### AI overview This tutorial explains how Retrieval-Augmented Generation combines large language models with external knowledge sources, and how Temporal and Chainlit can help build durable, reliable, scalable conversational AI workflows. ### Source excerpt Learn about how Temporal's durable execution framework can help solve this problem by bringing durability and resiliency into multi-step RAG workflows. ## Securing Infrastructure in Healthcare: Reducing Breaches and Building Resiliency DevFeed: [Securing Infrastructure in Healthcare: Reducing Breaches and Building Resiliency]() Original publisher: [Read original article]() Author: jack.pitts@goteleport.com (Jack Pitts) Published: 2024-09-03T00:00:00Z Content type: article Language: en Sources: [Teleport]() Topics: [Security, Privacy and Abuse Prevention](), [Security](), [Access Control](), [audit](), [resiliency](), [Databases](), [Network](), [Server]() Tags: [access-control](), [audit](), [data](), [data-privacy](), [healthcare](), [healthtech](), [hipaa](), [infrastructure](), [network](), [resiliency](), [security]() ### AI overview This article examines infrastructure, security, privacy, and compliance challenges faced by digital healthcare companies operating telehealth and remote patient monitoring systems. It uses a fictional company to discuss remote device access, data transmission, role-based access control, databases, and audit logging for HIPAA compliance, and describes how Teleport is presented as a solution. ### Source excerpt Ensure HIPAA compliance, protect patient data, and streamline telehealth access. Learn how HealthTech Innovations uses Teleport to overcome infrastructure challenges. ## Comparing Snapshot-Based and Diff-Based Data Syncs DevFeed: [Comparing Snapshot-Based and Diff-Based Data Syncs]() Original publisher: [Read original article]() Author: Sam Shen Published: 2024-08-07T18:51:01Z Content type: article Language: en Sources: [Clever]() Topics: [data](), [debugging]() Tags: [blog](), [data](), [engineering](), [interoperability](), [resiliency](), [syncs]() ### AI overview Clever compares two approaches to data synchronization using a grocery-shopping analogy. The supplied text explains that snapshot-based syncing can require large source and destination snapshots, while also making debugging and uniqueness checks easier. ### Source excerpt At Clever we move a lot of data, both from school districts into Clever and from Clever into all the external places that school districts want that data shared. Broadly, we call this behavior "syncing", and various sync flavors show up across Clever. Let's talk about two ways to perform data syncs by using an [...] The post Everything but the Kitchen Sync appeared first on Clever Engineering Blog. ## A stepping stone towards holistic application risk and compliance management of the Digital Operational Resiliency Act (DORA) DevFeed: [A stepping stone towards holistic application risk and compliance management of the Digital Operational Resiliency Act (DORA)]() Original publisher: [Read original article]() Author: Ben Desjardins; Mathias Conradt Published: 2024-07-11T05:00:00Z Content type: article Language: en Sources: [Blog RSS Feed | Snyk]() Topics: [Application Security](), [Resilience](), [Security](), [Vulnerabilities](), [ai-coding](), [Development](), [Deployment]() Tags: [ai-coding](), [application-security](), [awareness](), [blog](), [compliance](), [deployment](), [development](), [devops](), [digital](), [executive](), [finserv](), [operational](), [pmm](), [resiliency](), [security](), [snyk-platform](), [vulnerabilities]() ### AI overview The article explains how the European Union's Digital Operational Resilience Act (DORA) addresses ICT-related risks and business continuity for financial institutions and critical service providers. It presents application security across the development, deployment, and maintenance lifecycle as foundational to DORA compliance, emphasizing application vulnerabilities, software complexity, rapid development, and unmanaged use of AI coding assistants as sources of operational risk. ### Source excerpt The European Union's Digital Operational Resilience Act (DORA) establishes a comprehensive framework to manage Information and Communication Technology (ICT) related risks and ensure business continuity for financial institutions and critical service providers. ## Increasing Resiliency in a Banking Sweep System DevFeed: [Increasing Resiliency in a Banking Sweep System]() Original publisher: [Read original article]() Author: James Heller Published: 2024-06-27T20:00:00Z Content type: article Language: en Sources: [Apartment 304]() Topics: [resiliency](), [Networks](), [Processes]() Tags: [apartment-304](), [banking](), [custom-software-solutions](), [devops](), [devops-engineer](), [financial](), [insurance](), [integration](), [network](), [operational](), [resiliency](), [software-architecture](), [software-development](), [software-engineer](), [workflows]() ### AI overview The article describes incrementally migrating a banking sweep network system to Temporal Workflow. It explains how the approach addressed stability and operational issues while avoiding the risk of a full rewrite and its single cut-over event. ### Source excerpt Incrementally migrate a banking sweep network system to a Temporal Workflow ## Enhancing sweep networks with Temporal Workflows for greater resiliency DevFeed: [Enhancing sweep networks with Temporal Workflows for greater resiliency]() Original publisher: [Read original article]() Author: James Heller Published: 2024-06-27T07:00:00Z Content type: article Language: en Sources: [Temporal Blog]() Topics: [resiliency](), [Scalability](), [Networks]() Tags: [how-to](), [network](), [operations](), [resiliency](), [scalability]() ### AI overview This article describes how Apartment 304 incrementally migrated a banking sweep network system to Temporal workflows. The approach addressed stability and operational issues without requiring a full rewrite, while Temporal's message passing supported piece-by-piece workflow migration and faster stability improvements. ### Source excerpt Improve the resiliency and scalability of your banking sweep network by migrating to Temporal workflows, ensuring seamless and efficient operations. ## High availability in Keycloak 24 DevFeed: [High availability in Keycloak 24]() Original publisher: [Read original article]() Author: Alexander Schwartz, Ryan Emerson Published: 2024-05-07T00:00:00Z Content type: article Language: en Sources: [Keycloak Blog]() Topics: [Keycloak](), [Availability](), [resiliency](), [Deployment](), [private cloud]() Tags: [availability](), [configuration](), [deployment](), [documentation](), [high-availability](), [idm](), [kerberos](), [keycloak](), [ldap](), [openid-connect](), [private-cloud](), [release](), [resiliency](), [saml](), [sso]() ### AI overview The article recaps a Devoxx France 2024 presentation on Keycloak's high-availability architecture. It explains Keycloak's multi-site capabilities for public and private clouds and notes that Keycloak 24 fully supports active/passive deployments with simpler configuration. ### Source excerpt A single sign on solution for your customers and employees shouldn't be a single-point-of-failure in your architecture. At Devoxx France 2024, Ryan Emerson and Alexander Schwartz presented, from an architects and developer perspective, how Keycloak approached the problem. They describe which architecture the Keycloak team chose, the challenges they faced and which tools helped along the way. The slides and the recorded video are linked below. Scroll down for additional links and details of the tasks we're currently working on to further enhance the architecture. A clustered Keycloak deployment in a single site or datacenter provides sufficient availability for many. However, an increasing number of organizations need to utilize multiple sites for improved resiliency or to meet legal requirements. In 2023, Keycloak overhauled its multi-site capabilities for public and private cloud infrastructures, tested them thoroughly and provided deployment blueprints to the community. As part of the release of Keycloak 24, an active/passive setup is now fully supported. Read more about it in the new high availability guide published as part of Keycloak's documentation, and get more tools and background information in the Keycloak Benchmark Project. Since the previous blog post which covered Keycloak 23, we have made the configuration of such a setup simpler, with fewer options required by Keycloak and the Keycloak Operator. Thank you to everyone who provided feedback along the way, and those who participated in our survey in early 2023 which guided us in the implementation of this setup. Still, the journey doesn't stop here: The team is now working on durable sessions across restarts and upgrades, and a simpler Infinispan architecture which aims to eventually support active/active. Follow these issues and discussions to stay up-to-date with the latest developments, and provide feedback on Keycloak's nightly builds. ## How Realtor.com Achieved Technological and Cultural Transformation with GraphQL DevFeed: [How Realtor.com Achieved Technological and Cultural Transformation with GraphQL]() Original publisher: [Read original article]() Author: Ishwari Lokare Published: 2024-04-23T16:14:56Z Content type: article Language: en Sources: [Apollo Blog]() Topics: [GraphQL](), [API](), [Architecture & Design](), [Microservices]() Tags: [api](), [apollo-federation](), [events](), [graphql](), [microservices](), [resiliency](), [tech-stack]() ### AI overview Realtor.com's GraphQL adoption journey focused on simplifying its technology stack and unifying APIs with GraphQL and Apollo Federation. The article describes the technical, organizational, and communication practices used to support the transition and scale the platform. ### Source excerpt Realtor.com is a trusted real estate listing platform that connects buyers and realtors for a seamless experience when renting, buying, or selling properties. At GraphQL Summit 2023, Suzy Julius and Cabe Waldrop -- SVP of Product and Engineering and Principal Engineer at Realtor.com -- discussed the company's GraphQL journey to simplify its tech stack and scale without compromising performance. ## Designing Event-Driven Systems for Failure Resilience DevFeed: [Designing Event-Driven Systems for Failure Resilience]() Original publisher: [Read original article]() Author: Elliot Forbes Published: 2023-07-20T00:00:00Z Content type: article Language: en Sources: [Encore Updates]() Topics: [event driven](), [systems](), [Latency](), [User Experience]() Tags: [cpu](), [database](), [event-driven](), [latency](), [resiliency](), [systems](), [user-experience]() ### AI overview This article examines failure cases in event-driven systems and discusses standard practices for guarding against them. It explains trade-offs including added latency, infrastructure management, and fees, while noting potential benefits in resiliency and architectural simplicity. It also describes how resource limits and unoptimized database queries can cause latency spikes that harm production services and user experience. ### Source excerpt Uncovering hidden dangers when designing Event-Driven Systems [Next page]()