ISBN: 9798868831768 - designing self-healing systems with .net: from resilience to autonomous recovery in modern software systems (10 resultados)

ISBN: 
Refinar con la Búsqueda avanzada

Filtrar la búsqueda

  • Libros (10)

  • Nuevo (10)

a

Intervalo de precios personalizado (EUR)

a

  • Idioma: Inglés

    Editorial: Apress, 2026

    9798868831768

    • Tapa blanda

    Librería: California Books, Miami, FL, Estados Unidos de AmericaCalifornia Books

    Vendedor de 5 estrellas
    Contactar con el vendedor

    Condición: Nuevo

    EUR 50,71

    Envío por EUR 2,74 
    Se envía dentro de Estados Unidos de America

    Cantidad disponible: Más de 20 disponibles

    Condición: New.

  • Idioma: Inglés

    Editorial: APress, US, 2026

    9798868831768

    • Tapa blanda

    Librería: Rarewaves.com USA, London, LONDO, Reino UnidoRarewaves.com USA

    Vendedor de 5 estrellas
    Contactar con el vendedor

    Condición: Nuevo

    EUR 57,78

     Gastos de envío gratis 
    Se envía de Reino Unido a Estados Unidos de America

    Cantidad disponible: Más de 20 disponibles

    Paperback. Condición: New. Software systems fail. The expensive part is not the failure itself but the recovery: manual restarts, replayed jobs, drained queues, and configuration changes performed under pressure at inconvenient hours. Most teams already know the corrective actions for their common incidents. What they lack is an architecture that can apply those actions without waiting for a human to intervene every time.This book brings recovery into the architecture. It treats self-healing as a design discipline and provides a reference architecture that organizes detection, decision, safety, execution, and verification into a coherent control loop. It then delivers a concrete reference implementation in .NET, mapping every architectural layer to explicit contracts and components that teams can study, adapt, and extend.The architecture is grounded in production experience on a large distributed platform that connected dozens of public administrations through document exchange flows. As external integrations multiplied, each new dependency brought failure modes that demanded their own detection logic and recovery strategies. The design described in these pages emerged from that growth, and the anecdotes, case studies, and decisions throughout the text reflect that origin.The treatment goes beyond cloud-native microservices. It covers monoliths, legacy systems, hybrid environments, batch processing, messaging, and queue-centered workloads. It addresses the operating model as well: governance, safety boundaries, adoption roadmap, anti-patterns, and organizational roles. No existing title combines a self-healing reference architecture with a .NET reference implementation, and I believe this book addresses a gap that practicing .NET architects will recognize.What You Will Learn:Design and implement a self-healing reference architecture in .NET, with explicit contracts for observation, detection, decision, safety, execution, and verification.Classify failure modes (stall, degradation, traffic absence, gray failure) and build composite detection rules that reduce false positives while catching real conditions.Design bounded recovery actions (restart, degraded mode, quarantine, replay, credential rotation) with safety guards, cooldowns, action budgets, and verification gates.Apply self-healing patterns across different deployment topologies: single deployable, API-worker pair, queue-centered tier, modular monolith, distributed services, and hybrid/legacy environments.Build the organizational operating model behind self-healing: governance, adoption roadmap, maturity assessment, incident integration, and team roles.Who This Book is ForThe primary audience is .NET software architects and senior developers who design and operate backend systems, distributed services, messaging platforms, and integration layers. These professionals deal with production reliability challenges and are looking for a structured approach to automated recovery beyond ad-hoc retry logic and restart scripts.…

  • Idioma: Inglés

    Editorial: Apress, 2026

    9798868831768

    • Tapa blanda

    Librería: Home-set, Mannheim, AlemaniaHome-set

    Vendedor de 5 estrellas
    Contactar con el vendedor

    Condición: Nuevo

    EUR 80,24

    Envío por EUR 49,90 
    Se envía de Alemania a Estados Unidos de America

    Cantidad disponible: 2 disponibles

    Softcover/Taschenbuch. Condición: Neu. Neuware, Lieferung aus Deutschland. Sprache: Englisch Gewicht in Gramm: 645.

  • Idioma: Inglés

    Editorial: APress, US, 2026

    9798868831768

    • Tapa blanda

    Librería: Rarewaves.com UK, London, Reino UnidoRarewaves.com UK

    Vendedor de 5 estrellas
    Contactar con el vendedor

    Condición: Nuevo

    EUR 62,65

    Envío por EUR 77,55 
    Se envía de Reino Unido a Estados Unidos de America

    Cantidad disponible: Más de 20 disponibles

    Paperback. Condición: New. Software systems fail. The expensive part is not the failure itself but the recovery: manual restarts, replayed jobs, drained queues, and configuration changes performed under pressure at inconvenient hours. Most teams already know the corrective actions for their common incidents. What they lack is an architecture that can apply those actions without waiting for a human to intervene every time.This book brings recovery into the architecture. It treats self-healing as a design discipline and provides a reference architecture that organizes detection, decision, safety, execution, and verification into a coherent control loop. It then delivers a concrete reference implementation in .NET, mapping every architectural layer to explicit contracts and components that teams can study, adapt, and extend.The architecture is grounded in production experience on a large distributed platform that connected dozens of public administrations through document exchange flows. As external integrations multiplied, each new dependency brought failure modes that demanded their own detection logic and recovery strategies. The design described in these pages emerged from that growth, and the anecdotes, case studies, and decisions throughout the text reflect that origin.The treatment goes beyond cloud-native microservices. It covers monoliths, legacy systems, hybrid environments, batch processing, messaging, and queue-centered workloads. It addresses the operating model as well: governance, safety boundaries, adoption roadmap, anti-patterns, and organizational roles. No existing title combines a self-healing reference architecture with a .NET reference implementation, and I believe this book addresses a gap that practicing .NET architects will recognize.What You Will Learn:Design and implement a self-healing reference architecture in .NET, with explicit contracts for observation, detection, decision, safety, execution, and verification.Classify failure modes (stall, degradation, traffic absence, gray failure) and build composite detection rules that reduce false positives while catching real conditions.Design bounded recovery actions (restart, degraded mode, quarantine, replay, credential rotation) with safety guards, cooldowns, action budgets, and verification gates.Apply self-healing patterns across different deployment topologies: single deployable, API-worker pair, queue-centered tier, modular monolith, distributed services, and hybrid/legacy environments.Build the organizational operating model behind self-healing: governance, adoption roadmap, maturity assessment, incident integration, and team roles.Who This Book is ForThe primary audience is .NET software architects and senior developers who design and operate backend systems, distributed services, messaging platforms, and integration layers. These professionals deal with production reliability challenges and are looking for a structured approach to automated recovery beyond ad-hoc retry logic and restart scripts.…

  • Idioma: Inglés

    Editorial: APress, Berkley, 2026

    9798868831768

    • Tapa blanda
    • Impresión bajo demanda

    Librería: Grand Eagle Retail, Bensenville, IL, Estados Unidos de AmericaGrand Eagle Retail

    Vendedor de 5 estrellas
    Contactar con el vendedor

    Condición: Nuevo

    EUR 53,52

     Gastos de envío gratis 
    Se envía dentro de Estados Unidos de America

    Cantidad disponible: 1 disponible

    Paperback. Condición: new. Paperback. Software systems fail. The expensive part is not the failure itself but the recovery: manual restarts, replayed jobs, drained queues, and configuration changes performed under pressure at inconvenient hours. Most teams already know the corrective actions for their common incidents. What they lack is an architecture that can apply those actions without waiting for a human to intervene every time.This book brings recovery into the architecture. It treats self-healing as a design discipline and provides a reference architecture that organizes detection, decision, safety, execution, and verification into a coherent control loop. It then delivers a concrete reference implementation in .NET, mapping every architectural layer to explicit contracts and components that teams can study, adapt, and extend.The architecture is grounded in production experience on a large distributed platform that connected dozens of public administrations through document exchange flows. As external integrations multiplied, each new dependency brought failure modes that demanded their own detection logic and recovery strategies. The design described in these pages emerged from that growth, and the anecdotes, case studies, and decisions throughout the text reflect that origin.The treatment goes beyond cloud-native microservices. It covers monoliths, legacy systems, hybrid environments, batch processing, messaging, and queue-centered workloads. It addresses the operating model as well: governance, safety boundaries, adoption roadmap, anti-patterns, and organizational roles. No existing title combines a self-healing reference architecture with a .NET reference implementation, and I believe this book addresses a gap that practicing .NET architects will recognize.What You Will Learn:Design and implement a self-healing reference architecture in .NET, with explicit contracts for observation, detection, decision, safety, execution, and verification.Classify failure modes (stall, degradation, traffic absence, gray failure) and build composite detection rules that reduce false positives while catching real conditions.Design bounded recovery actions (restart, degraded mode, quarantine, replay, credential rotation) with safety guards, cooldowns, action budgets, and verification gates.Apply self-healing patterns across different deployment topologies: single deployable, API-worker pair, queue-centered tier, modular monolith, distributed services, and hybrid/legacy environments.Build the organizational operating model behind self-healing: governance, adoption roadmap, maturity assessment, incident integration, and team roles.Who This Book is ForThe primary audience is .NET software architects and senior developers who design and operate backend systems, distributed services, messaging platforms, and integration layers. These professionals deal with production reliability challenges and are looking for a structured approach to automated recovery beyond ad-hoc retry logic and restart scripts. This item is printed on demand. Shipping may be from multiple locations in the US or from the UK, depending on stock availability.…

  • Idioma: Inglés

    Editorial: Apress Jan 2027, 2027

    9798868831768

    • Tapa blanda
    • Impresión bajo demanda

    Librería: BuchWeltWeit Ludwig Meier e.K., Bergisch Gladbach, AlemaniaBuchWeltWeit Ludwig Meier e.K.

    Vendedor de 5 estrellas
    Contactar con el vendedor

    Condición: Nuevo

    EUR 64,19

    Envío por EUR 23,00 
    Se envía de Alemania a Estados Unidos de America

    Cantidad disponible: 2 disponibles

    Taschenbuch. Condición: Neu. This item is printed on demand - it takes 3-4 days longer - Neuware -Software systems fail. The expensive part is not the failure itself but the recovery: manual restarts, replayed jobs, drained queues, and configuration changes performed under pressure at inconvenient hours. Most teams already know the corrective actions for their common incidents. What they lack is an architecture that can apply those actions without waiting for a human to intervene every time.This book brings recovery into the architecture. It treats self-healing as a design discipline and provides a reference architecture that organizes detection, decision, safety, execution, and verification into a coherent control loop. It then delivers a concrete reference implementation in .NET, mapping every architectural layer to explicit contracts and components that teams can study, adapt, and extend.The architecture is grounded in production experience on a large distributed platform that connected dozens of public administrations through document exchange flows. As external integrations multiplied, each new dependency brought failure modes that demanded their own detection logic and recovery strategies. The design described in these pages emerged from that growth, and the anecdotes, case studies, and decisions throughout the text reflect that origin.The treatment goes beyond cloud-native microservices. It covers monoliths, legacy systems, hybrid environments, batch processing, messaging, and queue-centered workloads. It addresses the operating model as well: governance, safety boundaries, adoption roadmap, anti-patterns, and organizational roles. No existing title combines a self-healing reference architecture with a .NET reference implementation, and I believe this book addresses a gap that practicing .NET architects will recognize.What You Will Learn:Design and implement a self-healing reference architecture in .NET, with explicit contracts for observation, detection, decision, safety, execution, and verification.Classify failure modes (stall, degradation, traffic absence, gray failure) and build composite detection rules that reduce false positives while catching real conditions.Design bounded recovery actions (restart, degraded mode, quarantine, replay, credential rotation) with safety guards, cooldowns, action budgets, and verification gates.Apply self-healing patterns across different deployment topologies: single deployable, API-worker pair, queue-centered tier, modular monolith, distributed services, and hybrid/legacy environments.Build the organizational operating model behind self-healing: governance, adoption roadmap, maturity assessment, incident integration, and team roles.Who This Book is ForThe primary audience is .NET software architects and senior developers who design and operate backend systems, distributed services, messaging platforms, and integration layers. These professionals deal with production reliability challenges and are looking for a structured approach to automated recovery beyond ad-hoc retry logic and restart scripts. 391 pp. Englisch.…

  • Idioma: Inglés

    Editorial: APress, 2026

    9798868831768

    • Tapa blanda
    • Impresión bajo demanda

    Librería: moluna, Greven, Alemaniamoluna

    Vendedor de 5 estrellas
    Contactar con el vendedor

    Condición: Nuevo

    EUR 52,37

    Envío por EUR 48,99 
    Se envía de Alemania a Estados Unidos de America

    Cantidad disponible: Más de 20 disponibles

    Condición: New. Dieser Artikel ist ein Print on Demand Artikel und wird nach Ihrer Bestellung fuer Sie gedruckt.

  • Idioma: Inglés

    Editorial: Apress, 2026

    9798868831768

    • Tapa blanda
    • Impresión bajo demanda

    Librería: AHA-BUCH GmbH, Einbeck, AlemaniaAHA-BUCH GmbH

    Vendedor de 5 estrellas
    Contactar con el vendedor

    Condición: Nuevo

    EUR 70,76

    Envío por EUR 35,00 
    Se envía de Alemania a Estados Unidos de America

    Cantidad disponible: 1 disponible

    Taschenbuch. Condición: Neu. nach der Bestellung gedruckt Neuware - Printed after ordering - Software systems fail. The expensive part is not the failure itself but the recovery: manual restarts, replayed jobs, drained queues, and configuration changes performed under pressure at inconvenient hours. Most teams already know the corrective actions for their common incidents. What they lack is an architecture that can apply those actions without waiting for a human to intervene every time.This book brings recovery into the architecture. It treats self-healing as a design discipline and provides a reference architecture that organizes detection, decision, safety, execution, and verification into a coherent control loop. It then delivers a concrete reference implementation in .NET, mapping every architectural layer to explicit contracts and components that teams can study, adapt, and extend.The architecture is grounded in production experience on a large distributed platform that connected dozens of public administrations through document exchange flows. As external integrations multiplied, each new dependency brought failure modes that demanded their own detection logic and recovery strategies. The design described in these pages emerged from that growth, and the anecdotes, case studies, and decisions throughout the text reflect that origin.The treatment goes beyond cloud-native microservices. It covers monoliths, legacy systems, hybrid environments, batch processing, messaging, and queue-centered workloads. It addresses the operating model as well: governance, safety boundaries, adoption roadmap, anti-patterns, and organizational roles. No existing title combines a self-healing reference architecture with a .NET reference implementation, and I believe this book addresses a gap that practicing .NET architects will recognize.What You Will Learn:Design and implement a self-healing reference architecture in .NET, with explicit contracts for observation, detection, decision, safety, execution, and verification.Classify failure modes (stall, degradation, traffic absence, gray failure) and build composite detection rules that reduce false positives while catching real conditions.Design bounded recovery actions (restart, degraded mode, quarantine, replay, credential rotation) with safety guards, cooldowns, action budgets, and verification gates.Apply self-healing patterns across different deployment topologies: single deployable, API-worker pair, queue-centered tier, modular monolith, distributed services, and hybrid/legacy environments.Build the organizational operating model behind self-healing: governance, adoption roadmap, maturity assessment, incident integration, and team roles.Who This Book is ForThe primary audience is .NET software architects and senior developers who design and operate backend systems, distributed services, messaging platforms, and integration layers. These professionals deal with production reliability challenges and are looking for a structured approach to automated recovery beyond ad-hoc retry logic and restart scripts. …

  • Idioma: Inglés

    Editorial: APress, Berkley, 2026

    9798868831768

    • Tapa blanda
    • Impresión bajo demanda

    Librería: CitiRetail, Stevenage, Reino UnidoCitiRetail

    Vendedor de 5 estrellas
    Contactar con el vendedor

    Condición: Nuevo

    EUR 62,66

    Envío por EUR 44,14 
    Se envía de Reino Unido a Estados Unidos de America

    Cantidad disponible: 1 disponible

    Paperback. Condición: new. Paperback. Software systems fail. The expensive part is not the failure itself but the recovery: manual restarts, replayed jobs, drained queues, and configuration changes performed under pressure at inconvenient hours. Most teams already know the corrective actions for their common incidents. What they lack is an architecture that can apply those actions without waiting for a human to intervene every time.This book brings recovery into the architecture. It treats self-healing as a design discipline and provides a reference architecture that organizes detection, decision, safety, execution, and verification into a coherent control loop. It then delivers a concrete reference implementation in .NET, mapping every architectural layer to explicit contracts and components that teams can study, adapt, and extend.The architecture is grounded in production experience on a large distributed platform that connected dozens of public administrations through document exchange flows. As external integrations multiplied, each new dependency brought failure modes that demanded their own detection logic and recovery strategies. The design described in these pages emerged from that growth, and the anecdotes, case studies, and decisions throughout the text reflect that origin.The treatment goes beyond cloud-native microservices. It covers monoliths, legacy systems, hybrid environments, batch processing, messaging, and queue-centered workloads. It addresses the operating model as well: governance, safety boundaries, adoption roadmap, anti-patterns, and organizational roles. No existing title combines a self-healing reference architecture with a .NET reference implementation, and I believe this book addresses a gap that practicing .NET architects will recognize.What You Will Learn:Design and implement a self-healing reference architecture in .NET, with explicit contracts for observation, detection, decision, safety, execution, and verification.Classify failure modes (stall, degradation, traffic absence, gray failure) and build composite detection rules that reduce false positives while catching real conditions.Design bounded recovery actions (restart, degraded mode, quarantine, replay, credential rotation) with safety guards, cooldowns, action budgets, and verification gates.Apply self-healing patterns across different deployment topologies: single deployable, API-worker pair, queue-centered tier, modular monolith, distributed services, and hybrid/legacy environments.Build the organizational operating model behind self-healing: governance, adoption roadmap, maturity assessment, incident integration, and team roles.Who This Book is ForThe primary audience is .NET software architects and senior developers who design and operate backend systems, distributed services, messaging platforms, and integration layers. These professionals deal with production reliability challenges and are looking for a structured approach to automated recovery beyond ad-hoc retry logic and restart scripts. This item is printed on demand. Shipping may be from our UK warehouse or from our Australian or US warehouses, depending on stock availability.…

  • Idioma: Inglés

    Editorial: APress, Berkley, 2026

    9798868831768

    • Tapa blanda
    • Impresión bajo demanda

    Librería: AussieBookSeller, Truganina, VIC, AustraliaAussieBookSeller

    Vendedor de 5 estrellas
    Contactar con el vendedor

    Condición: Nuevo

    EUR 100,08

    Envío por EUR 33,74 
    Se envía de Australia a Estados Unidos de America

    Cantidad disponible: 1 disponible

    Paperback. Condición: new. Paperback. Software systems fail. The expensive part is not the failure itself but the recovery: manual restarts, replayed jobs, drained queues, and configuration changes performed under pressure at inconvenient hours. Most teams already know the corrective actions for their common incidents. What they lack is an architecture that can apply those actions without waiting for a human to intervene every time.This book brings recovery into the architecture. It treats self-healing as a design discipline and provides a reference architecture that organizes detection, decision, safety, execution, and verification into a coherent control loop. It then delivers a concrete reference implementation in .NET, mapping every architectural layer to explicit contracts and components that teams can study, adapt, and extend.The architecture is grounded in production experience on a large distributed platform that connected dozens of public administrations through document exchange flows. As external integrations multiplied, each new dependency brought failure modes that demanded their own detection logic and recovery strategies. The design described in these pages emerged from that growth, and the anecdotes, case studies, and decisions throughout the text reflect that origin.The treatment goes beyond cloud-native microservices. It covers monoliths, legacy systems, hybrid environments, batch processing, messaging, and queue-centered workloads. It addresses the operating model as well: governance, safety boundaries, adoption roadmap, anti-patterns, and organizational roles. No existing title combines a self-healing reference architecture with a .NET reference implementation, and I believe this book addresses a gap that practicing .NET architects will recognize.What You Will Learn:Design and implement a self-healing reference architecture in .NET, with explicit contracts for observation, detection, decision, safety, execution, and verification.Classify failure modes (stall, degradation, traffic absence, gray failure) and build composite detection rules that reduce false positives while catching real conditions.Design bounded recovery actions (restart, degraded mode, quarantine, replay, credential rotation) with safety guards, cooldowns, action budgets, and verification gates.Apply self-healing patterns across different deployment topologies: single deployable, API-worker pair, queue-centered tier, modular monolith, distributed services, and hybrid/legacy environments.Build the organizational operating model behind self-healing: governance, adoption roadmap, maturity assessment, incident integration, and team roles.Who This Book is ForThe primary audience is .NET software architects and senior developers who design and operate backend systems, distributed services, messaging platforms, and integration layers. These professionals deal with production reliability challenges and are looking for a structured approach to automated recovery beyond ad-hoc retry logic and restart scripts. This item is printed on demand. Shipping may be from our Sydney, NSW warehouse or from our UK or US warehouse, depending on stock availability.…