Cliquer sur une vignette pour aller sur Google Books.
Chargement... Release It!: Design and Deploy Production-Ready Software (2007)par Michael T. Nygard
Aucun Chargement...
Inscrivez-vous à LibraryThing pour découvrir si vous aimerez ce livre Actuellement, il n'y a pas de discussions au sujet de ce livre. A must-read book for any software developer. ( ) It was written in 2007, and it is starting to show its age in several respects. Despite this, there is still a lot of relevant advice on how to make software work well in production. For me, the best parts of the book were the cases studies, and the recommendations in the Stability chapters. There is some repetition in parts of the book, and it feels a bit dated at times. For example, several issues in the last chapter, like monitoring and continuous delivery seem to have become standard practice by now. Nevertheless, it is a worthwhile read, especially these days when more and more developers also operate the systems they develop. Full review on my blog: https://henrikwarne.com/2016/10/27/book-review-release-it/ This book is amazing. If you are a person who is responsible for the operations, uptime, stability, responsibity of the system you write, or you are a developer who is being told you should care, this is the book for you. It goes into understanding your system not just as the little piece of code you write but as a large thing with many moving parts that someone has to care about. It shows what to care about in the large ,but also how you can take that care and convert it into decisions and designs to make down at the individual component level. All this time it's filled with lived experience, and the book is 100% designed for he practical, not the idealogical or theoretical. Like probably many people, I became a devops person because I was the sucker who wasn't afraid of deploying the code on a unix server or who wasn't afraid to debug a working system in the late evening. As such I didn't have a formal or even learned ops background. This book is one of the things this year that I feel has actually qualified me to say I'm an ops person and not just a dev who plays one from time to time. Great companion to Continuous Delivery. Covers more of the development and architecture side of things and, again, should be required reading for every architect and senior developer. Don't agree with everything he says about database deployment; declarative development is much more useful than trying to code state transitions, especially when structure is in transition. aucune critique | ajouter une critique
Appartient à la série éditorialePrix et récompenses
A single dramatic software failure can cost a company millions of dollars - but can be avoided with simple changes to design and architecture. This new edition of the best-selling industry standard shows you how to create systems that run longer, with fewer failures, and recover better when bad things happen. New coverage includes DevOps, microservices, and cloud-native architecture. Stability antipatterns have grown to include systemic problems in large-scale systems. This is a must-have pragmatic guide to engineering for production systems. If you're a software developer, and you don't want to get alerts every night for the rest of your life, help is here. With a combination of case studies about huge losses - lost revenue, lost reputation, lost time, lost opportunity - and practical, down-to-earth advice that was all gained through painful experience, this book helps you avoid the pitfalls that cost companies millions of dollars in downtime and reputation. Eighty percent of project life-cycle cost is in production, yet few books address this topic. This updated edition deals with the production of today's systems - larger, more complex, and heavily virtualized - and includes information on chaos engineering, the discipline of applying randomness and deliberate stress to reveal systematic problems. Build systems that survive the real world, avoid downtime, implement zero-downtime upgrades and continuous delivery, and make cloud-native applications resilient. Examine ways to architect, design, and build software - particularly distributed systems - that stands up to the typhoon winds of a flash mob, a Slashdotting, or a link on Reddit. Take a hard look at software that failed the test and find ways to make sure your software survives. To skip the pain and get the experience...get this book. Aucune description trouvée dans une bibliothèque |
Discussion en coursAucunCouvertures populaires
Google Books — Chargement... GenresClassification décimale de Melvil (CDD)005.1Information Computing and Information Computer programming, programs, data, security ProgrammingClassification de la Bibliothèque du CongrèsÉvaluationMoyenne:
Est-ce vous ?Devenez un(e) auteur LibraryThing. |