This ever-improving artifact, beyond being authoritative, is also enjoying wide readership across the world.Architects, managers, and CIOs alike, have stopped me in conference hallways to talk about how refreshingly lucid the writing style is, with some painfully detailed illustrations, visio diagrams, and pictorials.With this first edition, we are converting Steve's blog into a book.The day we stop adding to this book is the beginning of the end of this company.Key characteristics of stand-alone servers included: Businesses always need to make money and data is a key piece of that puzzle.With direct-attached storage (DAS), organizations either needed more space than was locally available, or data high availability (HA) where a server failure wouldn’t cause data unavailability.
Democratizing our distributed architecture was not going to be easy in a world where most IT practitioners have been buried in dealing with the "urgent".
The concepts of distributed systems and software-led infrastructure are critical for IT practitioners to understand.
I encourage both Nutanix customers and everyone who wants to understand these trends to read the book.
Copyright (c) 2018: The Nutanix Bible and Nutanix Bible.com, 2018.
Unauthorized use and/or duplication of this material without express and written permission from this blog’s author and/or owner is strictly prohibited. Send feedback to biblefeedback at nutanix dot com Localized versions available: I am honored to write a foreword for this book that we've come to call "The Nutanix Bible." First and foremost, let me address the name of the book, which to some would seem not fully inclusive vis-à-vis their own faiths, or to others who are agnostic or atheist.
Steve epitomizes culture in this company -- by helping everyone else out with his authority on the subject, by helping them automate their chores in Power Shell or Python, by building insightful reference architectures (that are beautifully balanced in both content and form), by being a real-time buddy to anyone needing help on Yammer or Twitter, by being transparent with engineers on the need to self-reflect and self-improve, and by being ambitious.