To share your reaction on this item, open the Amazon app from the App Store or Google Play on your phone.
Add Prime to get Fast, Free delivery
Amazon prime logo
Buy new:
-54% $30.63
FREE delivery Friday, January 24 on orders shipped by Amazon over $35
Ships from: Amazon.com
Sold by: Amazon.com
$30.63 with 54 percent savings
List Price: $65.99
Get Fast, Free Shipping with Amazon Prime FREE Returns
FREE delivery Friday, January 24 on orders shipped by Amazon over $35
Or Prime members get FREE delivery Tuesday, January 21. Order within 1 hr 5 mins.
Only 4 left in stock (more on the way).
$$30.63 () Includes selected options. Includes initial monthly payment and selected options. Details
Price
Subtotal
$$30.63
Subtotal
Initial payment breakdown
Shipping cost, delivery date, and order total (including tax) shown at checkout.
Ships from
Amazon.com
Amazon.com
Ships from
Amazon.com
Sold by
Amazon.com
Amazon.com
Sold by
Amazon.com
Returns
30-day refund/replacement
30-day refund/replacement
This item can be returned in its original condition for a full refund or replacement within 30 days of receipt.
Payment
Secure transaction
Your transaction is secure
We work hard to protect your security and privacy. Our payment security system encrypts your information during transmission. We don’t share your credit card details with third-party sellers, and we don’t sell your information to others. Learn more
$25.54
May have limited writing in cover pages. Pages are unmarked. ~ ThriftBooks: Read More, Spend Less May have limited writing in cover pages. Pages are unmarked. ~ ThriftBooks: Read More, Spend Less See less
FREE delivery January 27 - 30. Details
Or fastest delivery January 24 - 28. Details
In stock
$$30.63 () Includes selected options. Includes initial monthly payment and selected options. Details
Price
Subtotal
$$30.63
Subtotal
Initial payment breakdown
Shipping cost, delivery date, and order total (including tax) shown at checkout.
Access codes and supplements are not guaranteed with used items.
Ships from and sold by ThriftBooks-Phoenix.
Kindle app logo image

Download the free Kindle app and start reading Kindle books instantly on your smartphone, tablet, or computer - no Kindle device required.

Read instantly on your browser with Kindle for Web.

Using your mobile phone camera - scan the code below and download the Kindle app.

QR code to download the Kindle App

Follow the author

Something went wrong. Please try your request again later.

DevOps Tools for Java Developers: Best Practices from Source Code to Production Containers 1st Edition

4.7 4.7 out of 5 stars 10 ratings

{"desktop_buybox_group_1":[{"displayPrice":"$30.63","priceAmount":30.63,"currencySymbol":"$","integerValue":"30","decimalSeparator":".","fractionalValue":"63","symbolPosition":"left","hasSpace":false,"showFractionalPartIfEmpty":true,"offerListingId":"dwxoBlV8dnmnNbUW89Fcp7xMqykksyMoHNGDET0s7MuXPJkZ38SrggIc9GuTLNPia2IL14vb0IRM5tietP%2FgE3dU6Y1dhAWVBpI7za9JZFJlx4B%2FJaMWNkyAoOHRsDvwQBrvFJOiqaF6u9G%2FafTFOQ%3D%3D","locale":"en-US","buyingOptionType":"NEW","aapiBuyingOptionIndex":0}, {"displayPrice":"$25.54","priceAmount":25.54,"currencySymbol":"$","integerValue":"25","decimalSeparator":".","fractionalValue":"54","symbolPosition":"left","hasSpace":false,"showFractionalPartIfEmpty":true,"offerListingId":"dwxoBlV8dnmnNbUW89Fcp7xMqykksyMoR%2F%2Bj6fOK93Jqn6apmFL4DmDgOWDjhp6wdDmoulO1fET2z1oAIXW2Hnf19ghKXkeI%2Ba9m%2BgkD2axGnETzC002qLPLggTX%2F1MiSpXJmHWZRgqWAZw1xU3LRn%2BOGrUkptT9yUemD18N6C9uPY%2BlHKltIiLtyN8h6xjQ","locale":"en-US","buyingOptionType":"USED","aapiBuyingOptionIndex":1}]}

Purchase options and add-ons

With the rise of DevOps, low-cost cloud computing, and container technologies, the way Java developers approach development today has changed dramatically. This practical guide helps you take advantage of microservices, serverless, and cloud native technologies using the latest DevOps techniques to simplify your build process and create hyperproductive teams.

Stephen Chin, Melissa McKay, Ixchel Ruiz, and Baruch Sadogursky from JFrog help you evaluate an array of options. The list includes source control with Git, build declaration with Maven and Gradle, CI/CD with CircleCI, package management with Artifactory, containerization with Docker and Kubernetes, and much more. Whether you're building applications with Jakarta EE, Spring Boot, Dropwizard, MicroProfile, Micronaut, or Quarkus, this comprehensive guide has you covered.

  • Explore software lifecycle best practices
  • Use DevSecOps methodologies to facilitate software development and delivery
  • Understand the business value of DevSecOps best practices
  • Manage and secure software dependencies
  • Develop and deploy applications using containers and cloud native technologies
  • Manage and administrate source control repositories and development processes
  • Use automation to set up and administer build pipelines
  • Identify common deployment patterns and antipatterns
  • Maintain and monitor software after deployment


From the brand


From the Publisher

DevOps Tools for Java Developers

From the Preface

This book was written in a time of immense change as the world was thrown upside down by the largest pandemic in a century. However, this work was never needed more as the software industry embraced DevOps and cloud native development to handle the accelerated pace of software delivery.

We organized this book so that the topics are in an incremental order of lifecycle, complexity, and maturity. However, DevOps is a broad enough journey that you may find some chapters more relevant than others for your project needs. As a result, we designed the chapters so that you can start in any order and focus on a particular subject for which you need expertise, examples, and best practices to advance your knowledge.

We hope you enjoy reading this title as much as we have enjoyed putting the content together. Our one ask is that you share your newfound knowledge with a friend or colleague so that we can all become better developers.

Editorial Reviews

About the Author

Stephen Chin is Head of Developer Relations at JFrog and author of The Definitive Guide to Modern Client Development, Raspberry Pi with Java, and Pro JavaFX Platform. He has keynoted numerous Java conferences around the world including Devoxx, JNation, JavaOne, Joker, and Open Source India. Stephen is an avid motorcyclist who has done evangelism tours in Europe, Japan, and Brazil, interviewing hackers in their natural habitat. When he is not traveling, he enjoys teaching kids how to do embedded and robot programming together with his teenage daughter. You can follow his hacking adventures at: http://steveonjava.com/.

Melissa McKay is currently a Developer Advocate with the JFrog Developer Relations team. She has been active in the software industry 20 years and her background and experience spans a slew of technologies and tools used in the development and operation of enterprise products and services. Melissa is a mom, software developer, Java geek, huge promoter of Java UNconferences, and is always on the lookout for ways to grow, learn, and improve development processes. She is active in the developer community, has spoken at CodeOne, Java Dev Day Mexico and assists with organizing the JCrete and JAlba Unconferences as well as Devoxx4Kids events.

Ixchel Ruiz has developed software applications and tools since 2000. Her research interests include Java, dynamic languages, client-side technologies, and testing. She is a Java Champion, Groundbreaker Ambassador, Hackergarten enthusiast, open source advocate, JUG leader, public speaker, and mentor.

Baruch Sadogursky (a.k.a JBaruch) is the Chief Sticker Officer @JFrog (also, Head of DevOps Advocacy) at JFrog. His passion is speaking about technology. Well, speaking in general, but doing it about technology makes him look smart, and 19 years of hi-tech experience sure helps. When he’s not on stage (or on a plane to get there), he learns about technology, people and how they work, or more precisely, don’t work together.

He is a co-author of the Liquid Software book, a CNCF ambassador and a passionate conference speaker on DevOps, DevSecOps, digital transformation, containers and cloud-native, artifact management and other topics, and is a regular at the industry’s most prestigious events including DockerCon, Devoxx, DevOps Days, OSCON, Qcon, JavaOne and many others. You can see some of his talks at jfrog.com/shownotes

Product details

  • Publisher ‏ : ‎ O'Reilly Media; 1st edition (May 24, 2022)
  • Language ‏ : ‎ English
  • Paperback ‏ : ‎ 341 pages
  • ISBN-10 ‏ : ‎ 1492084026
  • ISBN-13 ‏ : ‎ 978-1492084020
  • Item Weight ‏ : ‎ 1.21 pounds
  • Dimensions ‏ : ‎ 7 x 0.72 x 9.19 inches
  • Customer Reviews:
    4.7 4.7 out of 5 stars 10 ratings

About the author

Follow authors to get new release updates, plus improved recommendations.
Baruch Sadogursky
Brief content visible, double tap to read full content.
Full content visible, double tap to read brief content.

Baruch Sadogursky (@jbaruch) did Java before it had generics, DevOps before there was Docker, and DevRel before it had a name. He started DevRel at JFrog when it was ten people and took it all the way to a successful $6B IPO by helping engineers solve problems. Now Baruch keeps helping engineers solve problems but also helps companies help engineers solve problems. He is a co-author of the "Liquid Software" and "DevOps Tools for Java Developers" books, serves on multiple conference program committees, and regularly speaks at numerous most prestigious industry conferences, including Kubecon, JavaOne (RIP), Devoxx, QCon, DevRelCon, DevOpsDays (all over), DevOops (not a typo) and others.

Customer reviews

4.7 out of 5 stars
10 global ratings

Review this product

Share your thoughts with other customers

Top reviews from the United States

  • Reviewed in the United States on October 11, 2022
    DevOps Tools for Java developers describes in detail the concepts, patterns, standards (and, of course... tools!) for the best DevOps practices that we must consider in the industry these days.

    The first impressions about the book come straight from its cover. And I'm not talking about that cute banded mongoose, but about the amazing authors.

    I had the opportunity (and the privilege) to meet them all in person and watch tons of their talks at the biggest events around the world, and can say they are all just incredible individuals. Besides all of them being Java Champions, they also have a long and deep history in the DevOps context.

    What I liked most about the book is its completeness. If you are just getting started with software development or if you are a developer with more than 20 years of experience like me, you'll definitely learn a lot from this book.

    Topics like DevOps fundamentals, containers best practices, and even monolith dissection are not hidden from you. The journey throughout the book also guides you to package management, security, and continuous deployment.

    Talking about deployment, the book's masterpiece is its deployment deep dive chapter, covering all practices and tools that matter when working with containers and Kubernetes, not letting behind what you should consider for logging, monitoring, tracing, high availability, and hybrid cloud architectures.

    So, if are a developer committed to your own responsibility to build and deliver awesome applications using Java, this book is must read for you.
  • Reviewed in the United States on October 3, 2022
    As a Java developer, and Java Champion, I’m very pleased with this book and I recommend it to any Java developer who is interested in getting better at what they do. Whether you’re interested in DevOps or not, this book contains plenty of useful information to help you write better code, thoroughly test it, and then deploy it more effectively and efficiently.
    I prefer reading this kind of book because it doesn’t just tell you what to do or which tool to use, it shows you different approaches (and describes the trade-offs) so you can pick the tool or process that makes the most sense for your team and situation.
    Full disclosure: I was sent a copy of the book by one of the authors.
    One person found this helpful
    Report
  • Reviewed in the United States on October 1, 2022
    Review of DevOps Tools for Java Developers

    I was happy to get the opportunity to review an early copy of this book. I suggested it would be an interesting read, given the accumulated tech and speaking experience of the authors.

    First, let me say that I know three of the four authors of this book rather well, and I’ve had many pleasant and intelligent discussions with them on several continents over the years. I have known Mr. Sadogursky and Ms. Ruiz since 2010 or so, and have been all over the northern hemisphere on the same conferences as them. Both of them have made major contributions to the field, and are been tireless advocates for the Java ecosystem. The same goes for Mr. Chin, whom I’ve had honor to work with when I was in the Java Language Team at Oracle. As a tech evangelist, Mr. Chin is both tireless and brilliantly creative. He totally knows his stuff. While I haven’t met Ms. McKay in person, I’m familiar with her impact on the industry as well, and it’s not hard for me to understand why she was elected a Java Champion.

    All four authors are indeed Java Champions elected by their peers, and the Java Champions are definitely not just a club for navel gazing and mutual admiration (at least in the case of the authors – it is more doubtful why I, myself, am a member of this fine group). Looking at the recent years’ rather few publications that are “must-have” texts on the Java ecosystem, most of them are written by Java Champions. It’s probably a good quality hallmark for these kinds of books. One of several examples of such a book is “Optimizing Java - Practical techniques for improving JVM application performance" (Evans, Newland, Gough) et al). While totally different in scope, both regarding depth and width, I have a feeling this book also fits in the same “important Java-related works” category.

    Many of the books I recommend about Java go deep, and leave no corner unexplored. The Evans book is a good example here. But instead, given the size of the Java DevOps and DevOps in general, this quartet goes wide, which I believe is the correct and only possible approach, if you want to teach the fundamentals the DevOps topic. It is a testament to the competence of the authors that they manage to spend the exact right amount of time on all the significant parts of the modern DevOps Java spectrum. They also confirm that Java definitely is the gold standard for DevOps today, due to its versatility, ease of use, power, ubiquity and wide selection of indispensable tools. Guiding the reader through so much without losing track of the big picture is a very impressive feat! Most of us neckbeards won’t stop describing any rabbit hole, until its design has been completely covered down to individual ones and zeros. This book avoids that trap, and because of that, it has my sincere admiration! Of course, phone book sized tomes can be written about DevOps in particular, and definitely about Java DevOps as well, but coming up with a shorter book, like this, which still has the information content it does is actually an even more impressive feat.

    One example of a potentially destructive practice taken for granted in software engineering is the strange divide between dev engineering and QA. I am convinced that it’s a completely artificial and a rather bad idea. Likely, we have gotten stuck in that for too long because it is a concept that works much better (and is also a necessary evil) in other engineering disciplines and classic manufacturing. Originally it was adopted as-is, as this was the only way we could get a familiar toolbox for our fledgling software construction science. At least that’s my theory.

    Time and time again, I have seen that having separate QA and development engineering in different teams, on different floors, with different management or even with different management on different continents, produces suboptimal results. It certainly makes sense that other parties need to test your software – you will yourself subconsciously avoid the interactions that break it, because, of course, you wrote it without thinking about them. That’s why it breaks. And this is the way it’s done, by necessity, in other engineering disciplines. However, if QA treats your software as a black box, huge elephant sized bugs will still sneak under the radar and into production. Hence, QA and dev are increasingly turning into each other. These days, we are almost taking it for granted that writing and testing software are pretty much the same job. Together they have evolved into the best-known holistic approach to good software engineering. The black boxes are going away. Or at least, it is natural for a software engineer to also open them, while checking them out.

    DevOps is part of a similar kind of fusion. The reason that the "sysadmin" role was created and traditionally is a separate role from development, is exactly the same. Keeping hardware and software running was actually, until quite recently, a skilled full-time job. Doing the equivalent in other engineering disciplines often still is. However, for the last decade or so, we have benefited from that border also getting fuzzy. Sysadmin jobs date back to punched card era. It’s natural, in a world where everything had to be kept on on-prem servers (and punched card readers), that someone has to spend all their time taking care of them.

    Today, however, we live it a world where we can dial up ephemeral computing power on demand. Containerization distributed source control, integration test frameworks, shared version artefact repositories and modern build systems are making it easier and easier to pretty much ensure that every change gets into production immediately, as well as keeping your software stable. And thanks to DevOps, the sysadmin role is also merging into the more generic “modern software engineer”. We can automate things that previously were repetitive error prone manual processes. Thanks to the plethora of tools, and to the breakthroughs in technology, we can separate complex parts of our systems into understandable parts that you can run and test separately and bring them together through orchestration. And Java has done more to enable this and thanks to the huge tool set, gotten further than any other platform. This is why concise book like this, but wide in scope, is so important. It does a great job introducing the best practice tools that have become our new industry standard. It also clearly describes various anti-patterns, often the result from management being sold a hot new buzzwords, but don’t understand the real benefits of throwing money at a working DevOps infrastructure.

    I feel that is quite impressive for a book like this one, that has so much territory to cover in relatively few pages, to manage to summarize a lot of what I was contemplating above in various ways. The authors’ historical background aligns well with my own understanding of the technological breakthroughs that make modern DevOps possible, especially in Java land.

    Containerization is explained with shallow dives into Docker and Kubernetes, with a relevant historical background.

    The concept of monoliths vs. microservices, and the most common antipatterns that I have encountered in various IT shops that claim to use "microservices" are summarized well. I belive it covers most of the pitfalls involved, but it does not lose itself in deep dives into any particular hole.

    The importance of distributed source control and continous integration is also explained in less than 30 pages, with references to modern build an source control systems. When something has become the gold standard, like Git and variants of GitFlow for distributed source control and work flow, we are told why, concisely and to the point. All product introductions always come with at least a brief example that make sense and sharpens the picture.

    The same goes for the parts about build systems, which forms a natural progression to the much more interesting chapter “Package Management”. Perhaps you are surprised that such a clinically boring sounding topic is one of the more interesting chapters in the book, but that’s definitely true here. Ixchel Ruiz manages to provide us with admirable detail, again while keeping to the concise and matter-of-fact style that the entire book does so well.

    One of the more complex chapters is the discussion about securing your binaries. Software security is a difficult animal to work with, as it runs as an orthogonal path across all other aspects of moderrn software development. It does not necessarily modularize well, and it can’t entirely be improved with a single category of method or tool. Neither can it be applied only in one place. Again, given the scope of the book, I still think the authors do an admirable job of leaving nothing critical out of their security overview.

    The final chapter in the book contains descriptions of several case studies, providing more complete examples of DevOps anti-patterns, which were explained at the generic level earlier. For me the chapter worked as a validation, confirming that I sort of understand the general picture of what constitutes correctly done DevOps today. Furthermore, with the use cases as a guide I could check the overall “resolution” of my knowledge.

    So, to summarize; this is a book that you can at least quick-read from front to back in an intense continuous session. It’s also a handy reference manual for the bare minimum about almost all common utilized for Java DevOps today. The chapters have a natural progression, for example, continuous integration leads to package management, which is simpler to digest after the run through of the most popular build systems and other aspects of CI/CD. However, they also work very well as independent modules, and you can read them in the order they interest you the most without losing much context. This also shows how wells structured and even the text is, and that it has a rather high information content, despite its brevity. I don’t think this is easy to pull off.

    If your organization works with Java, but your team hasn’t gone that deep into DevOps land until now, no matter if some other part of your org handles that responsibility or if you need immediate improvements to your production pipeline, but don’t know where to begin, this book is a great place to start!

    The book will not make you a DevOps expert, but it will certainly hold your hand, show you the map, and provide you with more than enough initial knowledge to turn into one. Again, this is a surprisngly complete world map, even though we aren’t shown every single street. I believe very much something like this is needed as a starting point, both for technical management and engineering, and since I also believe this is exactly what the authors tried to do. I applaud them for being successful.
    2 people found this helpful
    Report

Top reviews from other countries

Translate all reviews to English
  • Lennart
    5.0 out of 5 stars Bon tour d’horizon bien structuré
    Reviewed in France on March 8, 2024
    J’ai acheté ce livre à moitié pour le plaisir et à moitié pour le désir de confronter mes usages à celui de développeurs expérimentés et ce livre ne m’a pas déçu.

    Même si le titre du livre est assez axé sur un usage précis, le contenu est structuré autour d’une présentation plus générale du Devops (ce n’est pas un vrai livre dessus mais c’est plutôt pour avoir une structure et un sens à l’usage qu’on en fait).

    Sur cette structure, le contenu est plutôt un tour d’horizon qu’un guide précis de chaque outil (le livre devrait faire 10 fois plus de pages). Le contenu est bien structuré en fonction des usages avec une progression logique.

    Bon, pour ma part j’avais déjà un usage assez proche mais j’ai quand même appris des choses et mis en perspective les outils.

    En somme, c’est un bon livre pour commencer à faire de la Devops sur ses projets Java (ou JVM) et obtenir un catalogue d’outils en précisant leurs usages. Si vous voulez apprendre un outil précis dans le détail, même si ce livre présente des snippets qui peuvent être largement suffisants pour se lancer, ce n’est pas lui qu’il faut acheter.

    Concernant l’écriture, j’ai apprécié le style et contrairement à certains livres O Reilly que j’ai lus, il n’y a quasiment pas de répétitions du contenu