Have we entered the age of NoOps infrastructures? Hardly. Old-style system administrators may be disappearing in the face of automation and cloud computing, but operations have become more significant than ever. As this O Reilly Radar Report explains, we re moving into a more complex arrangement known as "DevOps."
Mike Loukides, O Reilly s VP of Content Strategy, provides an incisive look into this new world of operations, where IT specialists are becoming part of the development team. In an environment with thousands of servers, these specialists now write the code that maintains the infrastructure. Even applications that run in the cloud have to be resilient and fault tolerant, need to be monitored, and must adjust to huge swings in load. That was underscored by Amazon s EBS outage last year.
From the discussions at O Reilly s Velocity Conference, it s evident that many operations specialists are quickly adapting to the DevOps reality. But as a whole, the industry has just scratched the surface. This report tells you why."
For me it felt like the author put more effort explaining how things were done in the past than elaborate on current practices, methods in IT culture now days.
Perfect explanation with very easy to understand articulation
For any IT professional, this book explains DevOps buzzword in easy to understand manner..It compares traditional world with newer age operations and it's closeness with development community
A quick 30 minutes read. But the title is misleading. It doesn't exactly explain what DevOps is, but rather why DevOps exists, and why NoOps is a misnomer.
it can be litle more in detail with some case studies to understand it much better. However with simple englidh it was easy to understand the basic concept
More information on Infrastructure as code should be explained. Overall the book covers the definition of Dev Ops and provides an insight to the process
A quick 30 minute read and as stated by others, more an essay than a book. It provides brief context on where the functions performed by DevOps arose from, then describes how those functions might be being performed today.
The emphasis on code as infrastructure is a key point and this is explained well against the background of today's technology. Overall, worth taking the time to read through for those wanting to understand the DevOps movement a little more.
This little essay can be read in 15 minutes and gives you a mirror to check if your organization is still living in the 80s.
It also shows how a lot of the questions of modern operations still lack a unique answer. It's a great moment to discover new ways of doing things and explore new technologies and methodologies.
This book provides a very high level overview of DevOps. However doesn't go into much details of DevOps concepts. It's good to start with this book if you are learning DevOps.
A gentle introduction to a politically fraught subject. At the very least, if it stops people getting hired as DevOps engineers, or DevOps departments getting created it will have done its job.
This book made me realize that I am doing DevOps. There are no distinctions anymore, and even large companies will not hire another resource for this when their development can handle the work.