Docker for Developers: Develop and run your application with Docker containers using DevOps tools for continuous delivery

As others have said, this book covers a lot of good material.Unfortunately, the code samples in the Kindle version are poorly formatted, and seem to be missing line breaks, resulting in difficult to read, run-on blobs of text. It's still technically possible to parse and understand the examples, but it's definitely more difficult than it should be.I think it may be due to a recent change in the Kindle app because I don't remember it being this way the first time I read the book, but referring back to it today, I see this problem on read.amazon.com (in Firefox and Chromium), and on the Kindle app for iPad.

Very completed with practical examples, tools and use cases.

The first section, chapters 5, 6 and 7 will look back on the history behind containerization. They will give you a very nice and humble introduction to Docker and container orchestration with a series of very minimalist and practical examples which lay down the foundation upon which the rest of the examples in the book will grow. I personally found them a very pleasant reading. From my experience as a professional developer working in projects built around Docker, the basic tools taught in these chapters pretty much sum up all that is needed to perform most if not all of the day-to-day tasks you may find in your own projects.Chapters 8, 9, 10 and 11 are going to give you a glance over what is necessary to get a professional Kubernetes cluster up on AWS with examples built on top of the work done thus far. There is a lot to digest in that and the knowledge is passed in a much faster pace, with less context as opposed to the previous chapters of the book. Don't get me wrong, there are tons of valuable information for those who haven't been exposed before to the Kubernetes and the wider ops world. However I didn't found them to be as didactic as the material I read to that point due to the very nature of the subject which is way denser, having a lot of non-trivial concepts to grasp which are not straightforward to tinker with. They will nonetheless give you a hands on exposure to the current industry best-practices, expand your perspective over the subject and leave you in a good place where you can continue learning on your own.The remaining pages will then finally give you a complete look on what to keep in mind when it comes to security in a container-based environment. You'll enjoy the tips in this third and last section which is full of practical advice to keep you, your company and your users protected from silly mistakes and the most common threats. You will learn about the security model around Docker and how to monitor your deployments with an eye on security. Overall the book seemed pretty worthy. As a developer myself, with daily tasks not really focused on most of the topics put forth in depth here, I found the reading very interesting. It has certainly improved my understanding around the topics covered. I recommend it.

When reading articles, tutorials and even books, that is very common that at the end of the reading you struggle about how to translate that to a real production situation. Believe me, this book is different. You get to the end with a sense that you are very likely to know what are the next steps to apply what you learned to your existent or new projects. And this means a lot. The book has some great balance from history, concepts, example and practice.Although there is a lot of cont to grasp and the book is not exhaustive about the subjects, it gives you the most important information and real-world scenarios. You will be confident about the path you need to go to improve your local environment, to prepare a CI/CD pipeline and ship your product to production with a high-quality workflow. The authors are careful enough to list different solutions and approaches because there is not a single tool that solves all the problems and this book give you enough to understand which stack could fit better to your software needs.If you want to know more about Docker on your local environment, how containers relate to production, container orchestration with Docker swarm or Kubernetes, container image publishing, etc, you need this book.I highly recommend it.

I read this book over the course of a week and deployed docker containers into our repositories over a two week period following that. Then, the week after that, I gave a lunch n learn to the company, using what I had l learned from the book and experience from practice. Now we have containers for clean e2e testing, gitlab docker runners to run and scale to more runners without new VMs, they build containers for us, and it’s quickly become normal in our company. I’ll be reviewing the kuberneties sections over the new week to keep down the path. Thanks Richard. This book cuts to the chase and lives up to the title!

The most appealing chapters for me were about Security. Docker for Developers provides an introduction to security then goes onto describing high-level concepts over multiple chapters. Citing resources online for further understanding into specific security topics. Helping the reader understand the breadth of considerations of what goes into security with docker when deploying. Wrapping understanding of the ecosystem that exists for different software solutions used to lock down systems running docker and protect against malicious intent

Doesn't really teach you how to use Docker. It just introduces a bunch of somewhat related technologies (at a shallow layer) that you can use Docker and Kubernetes with.

This is a good book - it's just not what I expected. What I _thought_ I'd get, based on the title, was a hands-on low-level nitty gritty ultra-geek caliber technical tour of all the ins and outs of working with Docker as a developer, in a day-to-day way (i.e. the best way to write docker files for various essential scenarios, the best coding practices, etc.).That's not what this book is. It does contain a bunch of pretty good technical information - but it's much more a guided tour of the entire Docker ecosystem (including a long list of related libs, products and services like Kubernetes, Jenkins, Grafana, Envoy, etc.), than it is a low-level developer guide.That's not bad, it's just not what I expected.It actually does a nice job of introducing just how broad the Docker-centric ecosystem really is, and outlining many of the most popular, useful, and important products/services/libs therein. If anything, it just covers too much breadth, and sacrifices depth as a result.My biggest complaint about this book is that the authors offloaded a TON, and I mean a LOOOOOT, of work to external sources (3rd party docs, etc.). It covers so much ground that if it didn't do that it would be a 900 page monster – but by lazily offloading SO MUCH lifting to external links, the book ends up being just a brief high-level intro to almost 2/3 of the various products and services it introduces - before pointing you to their external docs with a note like, "To learn about [this], go [here] and read [this page]." ... then immediately after the URL on the page they continue with , "...OK, so now that you've learned how to do [that], let's move on to [the next thing]...".In too many cases, this book doesn't actually *teach* you much of anything. It just sorta explains that this product can do this thing, and you can read about it here, and this is why that's important and you should learn and use it in your container app. The authors assume those third parties will explain all you need to know about how their stuff works, and that you'll be resourceful enough to dig thru their external docs to answer any questions you may have, etc.Beyond Docker itself, the book's best coverage is around Kubernetes, Jenkins, and AWS EKS - and these are massively useful and important. But the rest of the products it refers to are, to borrow a term the authors themselves use more than once, a very quick "whistle stop tour."There's plenty of value in this book, and I do recommend it. I just want you to know what it is, and what it is not.

I ch bin ganz begeistert.