IniciGrupsConversesMésTendències
Cerca al lloc
Aquest lloc utilitza galetes per a oferir els nostres serveis, millorar el desenvolupament, per a anàlisis i (si no has iniciat la sessió) per a publicitat. Utilitzant LibraryThing acceptes que has llegit i entès els nostres Termes de servei i política de privacitat. L'ús que facis del lloc i dels seus serveis està subjecte a aquestes polítiques i termes.
Hide this

Resultats de Google Books

Clica una miniatura per anar a Google Books.

S'està carregant…

Release It!: Design and Deploy Production-Ready Software

de Michael T. Nygard

MembresRessenyesPopularitatValoració mitjanaConverses
349555,627 (4.3)No n'hi ha cap
Whether it's in Java, .NET, or Ruby on Rails, getting your application ready to ship is only half the battle. Did you design your system to survivef a sudden rush of visitors from Digg or Slashdot? Or an influx of real world customers from 100 different countries? Are you ready for a world filled with flakey networks, tangled databases, and impatient users? If you're a developer and don't want to be on call for 3AM for the rest of your life, this book will help. In Release It!, Michael T. Nygard shows you how to design and architect your application for the harsh realities it will face. You'll learn how to design your application for maximum uptime, performance, and return on investment. Mike explains that many problems with systems today start with the design.… (més)
No n'hi ha cap
S'està carregant…

Apunta't a LibraryThing per saber si aquest llibre et pot agradar.

No hi ha cap discussió a Converses sobre aquesta obra.

Es mostren totes 5
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/ ( )
  Henrik_Warne | Dec 13, 2020 |
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. ( )
  NaleagDeco | Dec 13, 2020 |
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. ( )
  djryan | Dec 18, 2012 |
A little disorganized, but for some reason I found this to be a really engaging book. How we'd actually be able to implement and "scale down" some of these tips to an organization of the size I work for isn't entirely clear. Obviously a good framework can make debugging and troubleshooting much easier, but there's also a level of expertise needed. It would have been interesting to see what experience he recommends as well or approaches for internal training.

The author is skewed towards Java and Unix machines, but it's not at a level where it interferes with the book. (Although I've used Java and I also use Unix/Linux machines so I'm a bit of a bad sample).

I'm tempted to give this book another read.
  JonathanGorman | Oct 31, 2009 |
Es mostren totes 5
Sense ressenyes | afegeix-hi una ressenya

Pertany a aquestes col·leccions editorials

Has d'iniciar sessió per poder modificar les dades del coneixement compartit.
Si et cal més ajuda, mira la pàgina d'ajuda del coneixement compartit.
Títol normalitzat
Informació del coneixement compartit en anglès. Modifica-la per localitzar-la a la teva llengua.
Títol original
Títols alternatius
Data original de publicació
Gent/Personatges
Llocs importants
Esdeveniments importants
Pel·lícules relacionades
Premis i honors
Informació del coneixement compartit en anglès. Modifica-la per localitzar-la a la teva llengua.
Epígraf
Dedicatòria
Primeres paraules
Citacions
Darreres paraules
Nota de desambiguació
Editor de l'editorial
Creadors de notes promocionals a la coberta
Llengua original
CDD/SMD canònics

Referències a aquesta obra en fonts externes.

Wikipedia en anglès (1)

Whether it's in Java, .NET, or Ruby on Rails, getting your application ready to ship is only half the battle. Did you design your system to survivef a sudden rush of visitors from Digg or Slashdot? Or an influx of real world customers from 100 different countries? Are you ready for a world filled with flakey networks, tangled databases, and impatient users? If you're a developer and don't want to be on call for 3AM for the rest of your life, this book will help. In Release It!, Michael T. Nygard shows you how to design and architect your application for the harsh realities it will face. You'll learn how to design your application for maximum uptime, performance, and return on investment. Mike explains that many problems with systems today start with the design.

No s'han trobat descripcions de biblioteca.

Descripció del llibre
Sumari haiku

Dreceres

Cobertes populars

Valoració

Mitjana: (4.3)
0.5
1 1
1.5
2 1
2.5
3 9
3.5 2
4 15
4.5 1
5 33

Ets tu?

Fes-te Autor del LibraryThing.

 

Quant a | Contacte | LibraryThing.com | Privadesa/Condicions | Ajuda/PMF | Blog | Botiga | APIs | TinyCat | Biblioteques llegades | Crítics Matiners | Coneixement comú | 157,746,136 llibres! | Barra superior: Sempre visible