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

Perfeziona la tua ricerca

  • Libri (10)

  • Nuovo (10)

a

Fascia di prezzo personalizzata (EUR)

a

  • Lingua: Inglese

    Editore: Apress, 2026

    9798868831768

    • Brossura

    Da: California Books, Miami, FL, U.S.A.California Books

    Venditore con 5 stelle
    Contatta il venditore

    Condizione: Nuovo

    EUR 50,71

    EUR 2,74 spedizione 
    Spedito in U.S.A.

    Quantità: Più di 20 disponibili

    Condizione: New.

  • Lingua: Inglese

    Editore: APress, US, 2026

    9798868831768

    • Brossura

    Da: Rarewaves.com USA, London, LONDO, Regno UnitoRarewaves.com USA

    Venditore con 5 stelle
    Contatta il venditore

    Condizione: Nuovo

    EUR 57,78

     Spedizione gratuita 
    Spedito da Regno Unito a U.S.A.

    Quantità: Più di 20 disponibili

    Paperback. Condizione: 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.…

  • Lingua: Inglese

    Editore: Apress, 2026

    9798868831768

    • Brossura

    Da: Home-set, Mannheim, GermaniaHome-set

    Venditore con 5 stelle
    Contatta il venditore

    Condizione: Nuovo

    EUR 80,24

    EUR 49,90 spedizione 
    Spedito da Germania a U.S.A.

    Quantità: 2 disponibili

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

  • Lingua: Inglese

    Editore: APress, US, 2026

    9798868831768

    • Brossura

    Da: Rarewaves.com UK, London, Regno UnitoRarewaves.com UK

    Venditore con 5 stelle
    Contatta il venditore

    Condizione: Nuovo

    EUR 62,65

    EUR 77,55 spedizione 
    Spedito da Regno Unito a U.S.A.

    Quantità: Più di 20 disponibili

    Paperback. Condizione: 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.…

  • Lingua: Inglese

    Editore: APress, Berkley, 2026

    9798868831768

    • Brossura
    • Print on Demand

    Da: Grand Eagle Retail, Bensenville, IL, U.S.A.Grand Eagle Retail

    Venditore con 5 stelle
    Contatta il venditore

    Condizione: Nuovo

    EUR 53,52

     Spedizione gratuita 
    Spedito in U.S.A.

    Quantità: 1 disponibile

    Paperback. Condizione: 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.…

  • Lingua: Inglese

    Editore: Apress Jan 2027, 2027

    9798868831768

    • Brossura
    • Print on Demand

    Da: BuchWeltWeit Ludwig Meier e.K., Bergisch Gladbach, GermaniaBuchWeltWeit Ludwig Meier e.K.

    Venditore con 5 stelle
    Contatta il venditore

    Condizione: Nuovo

    EUR 64,19

    EUR 23,00 spedizione 
    Spedito da Germania a U.S.A.

    Quantità: 2 disponibili

    Taschenbuch. Condizione: 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.…

  • Lingua: Inglese

    Editore: APress, 2026

    9798868831768

    • Brossura
    • Print on Demand

    Da: moluna, Greven, Germaniamoluna

    Venditore con 5 stelle
    Contatta il venditore

    Condizione: Nuovo

    EUR 52,37

    EUR 48,99 spedizione 
    Spedito da Germania a U.S.A.

    Quantità: Più di 20 disponibili

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

  • Lingua: Inglese

    Editore: Apress, 2026

    9798868831768

    • Brossura
    • Print on Demand

    Da: AHA-BUCH GmbH, Einbeck, GermaniaAHA-BUCH GmbH

    Venditore con 5 stelle
    Contatta il venditore

    Condizione: Nuovo

    EUR 70,76

    EUR 35,00 spedizione 
    Spedito da Germania a U.S.A.

    Quantità: 1 disponibile

    Taschenbuch. Condizione: 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.…

  • Lingua: Inglese

    Editore: APress, Berkley, 2026

    9798868831768

    • Brossura
    • Print on Demand

    Da: CitiRetail, Stevenage, Regno UnitoCitiRetail

    Venditore con 5 stelle
    Contatta il venditore

    Condizione: Nuovo

    EUR 62,66

    EUR 44,14 spedizione 
    Spedito da Regno Unito a U.S.A.

    Quantità: 1 disponibile

    Paperback. Condizione: 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.…

  • Lingua: Inglese

    Editore: APress, Berkley, 2026

    9798868831768

    • Brossura
    • Print on Demand

    Da: AussieBookSeller, Truganina, VIC, AustraliaAussieBookSeller

    Venditore con 5 stelle
    Contatta il venditore

    Condizione: Nuovo

    EUR 100,08

    EUR 33,74 spedizione 
    Spedito da Australia a U.S.A.

    Quantità: 1 disponibile

    Paperback. Condizione: 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.…