menu
{ "item_title" : "The Orchestrator", "item_author" : [" Javid Ur Rahaman "], "item_description" : "Orchestration is taught almost nowhere as a coherent subject. It is picked up in fragments - a database module here, a reliability elective there, a certification bought by an employer. The barrier is structural: almost every serious text in the field is bound to one product line, so teaching it means licensing a stack, rewriting the syllabus every release, and watching the material expire. Orchestrator removes that barrier. It names no products. It reasons instead in five generic tiers - ERP, APP, WEB, DB and INTEGRATION - and in the properties that actually decide outcomes: protection mode, loss budget, transport lag, apply lag, arbitration authority, quorum, fencing, evidence. Ten chapters across a four-part spine. FOUNDATIONS establishes the discipline and the forty-year arc that produced it. THE ESTATE confronts the estate as it is, and makes the book's central claim: resilience is decided in the seams between tiers, not inside any one of them. DESIGN gives eight structural patterns and the abstractions they rest on. OPERATION covers preemptive switchover, compilable runbooks, chaos verification, the evidence record, and how to measure any of it honestly. WRITTEN TO BE TAUGHT. Every chapter carries learning outcomes with observable verbs, two design labs that run on open-source components with no commercial licence required, six review questions, and five closing framings that double as a marking rubric. Thirty-five monochrome figures - architecture diagrams, workflows, concept maps and decision matrices - every one with alternative text. WRITTEN TO BE PLACED. A standards register maps the material to ITIL, TOGAF, COBIT, ISO 22301, ISO/IEC 27001, the NIST frameworks and the EU resilience instruments, and names the places where this book asks for more than the framework does. The core sequence sits at FHEQ Level 5 and EQF Level 5, with notional learning hours for ECTS costing. For community college and undergraduate IT programs, faculty and course designers, academic and public libraries, researchers, boards and executives, and the engineers who will run these estates next.", "item_img_path" : "https://covers2.booksamillion.com/covers/bam/9/79/819/178/9798191784809_b.jpg", "price_data" : { "retail_price" : "20.00", "online_price" : "20.00", "our_price" : "20.00", "club_price" : "20.00", "savings_pct" : "0", "savings_amt" : "0.00", "club_savings_pct" : "0", "club_savings_amt" : "0.00", "discount_pct" : "10", "store_price" : "" } }
The Orchestrator|Javid Ur Rahaman

The Orchestrator : A Handbook for Future Engineers - High Availability, Disaster Recovery, and Governed Control

local_shippingShip to Me
In Stock.
FREE Shipping for Club Members help

Overview

Orchestration is taught almost nowhere as a coherent subject. It is picked up in fragments - a database module here, a reliability elective there, a certification bought by an employer. The barrier is structural: almost every serious text in the field is bound to one product line, so teaching it means licensing a stack, rewriting the syllabus every release, and watching the material expire. Orchestrator removes that barrier. It names no products. It reasons instead in five generic tiers - ERP, APP, WEB, DB and INTEGRATION - and in the properties that actually decide outcomes: protection mode, loss budget, transport lag, apply lag, arbitration authority, quorum, fencing, evidence. Ten chapters across a four-part spine. FOUNDATIONS establishes the discipline and the forty-year arc that produced it. THE ESTATE confronts the estate as it is, and makes the book's central claim: resilience is decided in the seams between tiers, not inside any one of them. DESIGN gives eight structural patterns and the abstractions they rest on. OPERATION covers preemptive switchover, compilable runbooks, chaos verification, the evidence record, and how to measure any of it honestly. WRITTEN TO BE TAUGHT. Every chapter carries learning outcomes with observable verbs, two design labs that run on open-source components with no commercial licence required, six review questions, and five closing framings that double as a marking rubric. Thirty-five monochrome figures - architecture diagrams, workflows, concept maps and decision matrices - every one with alternative text. WRITTEN TO BE PLACED. A standards register maps the material to ITIL, TOGAF, COBIT, ISO 22301, ISO/IEC 27001, the NIST frameworks and the EU resilience instruments, and names the places where this book asks for more than the framework does. The core sequence sits at FHEQ Level 5 and EQF Level 5, with notional learning hours for ECTS costing. For community college and undergraduate IT programs, faculty and course designers, academic and public libraries, researchers, boards and executives, and the engineers who will run these estates next.

This item is Non-Returnable

Details

  • ISBN-13: 9798191784809
  • ISBN-10: 9798191784809
  • Publisher: Independently Published
  • Publish Date: August 2026
  • Dimensions: 9 x 6 x 1.19 inches
  • Shipping Weight: 1.26 pounds
  • Page Count: 478

Related Categories

You May Also Like...

    1

BAM Customer Reviews