Amazon cover image
Image from Amazon.com

Continuous delivery in Java : essential tools and best practices for deploying code to production / Daniel Bryant and Abraham Marín-Pérez.

By: Contributor(s): Publisher: Beijing : O'Reilly Media, ©2018Edition: First editionDescription: xxiii,453pContent type:
  • text
Media type:
  • computer
Carrier type:
  • online resource
ISBN:
  • 9781491986028 (print)
Subject(s): Genre/Form: Additional physical formats: Print version:: Continuous delivery in Java :LOC classification:
  • QA76.76 .A65 B79 2018
Contents:
Cover; Copyright; Table of Contents; Forewords; Preface; Why Did We Write This Book?; Why You Should Read This Book; What This Book Is Not; Conventions Used in This Book; Using Code Examples; O'Reilly Safari; How to Contact Us; Acknowledgments; Chapter 1. Continuous Delivery: Why and What; Setting the Scene; Enabling Developers: The Why; Rapid Feedback Reduces Context Switching; Automatic, Repeatable, and Reliable Releases; Codifying the Definition of "Done"; Exploring a Typical Build Pipeline: The What; Core Build Pipeline Stages; Impact of Container Technology.
Changes with Contemporary ArchitecturesSummary; Chapter 2. Evolution of Java Development; Requirements of Modern Java Applications; Need for Business Speed and Stability; Rise of the API Economy; Opportunities and Costs of the Cloud; Modularity Redux: Embracing Small Services; Impact on Continuous Delivery; Evolution of Java Deployment Platforms; WARs and EARs: The Era of Application Server Dominance; Executable Fat JARs: Emergence of Twelve-Factor Apps; Container Images: Increasing Portability (and Complexity); Function as a Service: The Emergence of "Serverless"
Impact of Platforms on Continuous DeliveryDevOps, SRE, and Release Engineering; Development and Operations; Site Reliability Engineering; Release Engineering; Shared Responsibility, Metrics, and Observability; Summary; Chapter 3. Designing Architecture for Continuous Delivery; Fundamentals of Good Architecture; Loose Coupling; High Cohesion; Coupling, Cohesion, and Continuous Delivery; Architecture for Business Agility; Bad Architecture Limits Business Velocity; Complexity and Cost of Change; Best Practices for API-Driven Applications; Build APIs "Outside-In"
Good APIs Assist Continuous Testing and DeliveryDeployment Platforms and Architecture; Designing Cloud-Native "Twelve-Factor" Applications; Cultivating Mechanical Sympathy; Design and Continually Test for Failure; The Move Toward Small Services; Challenges for Delivering Monolithic Applications; Microservices: SOA Meets Domain-Driven Design; Functions, Lambdas, and Nanoservices; Architecture: "The Stuff That's Hard to Change"; Summary; Chapter 4. Deployment Platforms, Infrastructure, and Continuous Delivery of Java Apps; Functionality Provided by a Platform; Essential Development Processes.
Traditional Infrastructure PlatformsTraditional Platform Components; Challenges with Traditional Infrastructure Platforms; Benefits of Being Traditional; CI/CD on Traditional Infrastructure Platforms; Cloud (IaaS) Platform; Looking Inside the Cloud; Cloud Challenges; Benefits of the Cloud; Continuously Delivering into the Cloud; Platform as a Service; Peeking Inside a PaaS; PaaS Challenges; Benefits of PaaS; CI/CD and PaaS; Containers (Docker); Container Platform Components; Container Challenges; Container Benefits; Continuously Delivering Containers; Kubernetes; Core Concepts of Kubernetes.
In: ProQuest Ebook Central (online collection). UNL. Title-by-title purchases. Via YBP
Item type: BOOKS
Star ratings
    Average rating: 0.0 (0 votes)
Holdings
Current library Home library Call number Status Barcode
Alfaisal University On Shelf Alfaisal University On Shelf QA76.76 .A65 B79 2018 (Browse shelf(Opens below)) Available AU00000000013717
Total holds: 0

Includes index.

Cover; Copyright; Table of Contents; Forewords; Preface; Why Did We Write This Book?; Why You Should Read This Book; What This Book Is Not; Conventions Used in This Book; Using Code Examples; O'Reilly Safari; How to Contact Us; Acknowledgments; Chapter 1. Continuous Delivery: Why and What; Setting the Scene; Enabling Developers: The Why; Rapid Feedback Reduces Context Switching; Automatic, Repeatable, and Reliable Releases; Codifying the Definition of "Done"; Exploring a Typical Build Pipeline: The What; Core Build Pipeline Stages; Impact of Container Technology.

Changes with Contemporary ArchitecturesSummary; Chapter 2. Evolution of Java Development; Requirements of Modern Java Applications; Need for Business Speed and Stability; Rise of the API Economy; Opportunities and Costs of the Cloud; Modularity Redux: Embracing Small Services; Impact on Continuous Delivery; Evolution of Java Deployment Platforms; WARs and EARs: The Era of Application Server Dominance; Executable Fat JARs: Emergence of Twelve-Factor Apps; Container Images: Increasing Portability (and Complexity); Function as a Service: The Emergence of "Serverless"

Impact of Platforms on Continuous DeliveryDevOps, SRE, and Release Engineering; Development and Operations; Site Reliability Engineering; Release Engineering; Shared Responsibility, Metrics, and Observability; Summary; Chapter 3. Designing Architecture for Continuous Delivery; Fundamentals of Good Architecture; Loose Coupling; High Cohesion; Coupling, Cohesion, and Continuous Delivery; Architecture for Business Agility; Bad Architecture Limits Business Velocity; Complexity and Cost of Change; Best Practices for API-Driven Applications; Build APIs "Outside-In"

Good APIs Assist Continuous Testing and DeliveryDeployment Platforms and Architecture; Designing Cloud-Native "Twelve-Factor" Applications; Cultivating Mechanical Sympathy; Design and Continually Test for Failure; The Move Toward Small Services; Challenges for Delivering Monolithic Applications; Microservices: SOA Meets Domain-Driven Design; Functions, Lambdas, and Nanoservices; Architecture: "The Stuff That's Hard to Change"; Summary; Chapter 4. Deployment Platforms, Infrastructure, and Continuous Delivery of Java Apps; Functionality Provided by a Platform; Essential Development Processes.

Traditional Infrastructure PlatformsTraditional Platform Components; Challenges with Traditional Infrastructure Platforms; Benefits of Being Traditional; CI/CD on Traditional Infrastructure Platforms; Cloud (IaaS) Platform; Looking Inside the Cloud; Cloud Challenges; Benefits of the Cloud; Continuously Delivering into the Cloud; Platform as a Service; Peeking Inside a PaaS; PaaS Challenges; Benefits of PaaS; CI/CD and PaaS; Containers (Docker); Container Platform Components; Container Challenges; Container Benefits; Continuously Delivering Containers; Kubernetes; Core Concepts of Kubernetes.

Access limited to UNC Chapel Hill-authenticated users. Unlimited simultaneous users.

Vendor-supplied catalog record.

Provider: ProQuest.

Copyright © 2020 Alfaisal University Library. All Rights Reserved.
Tel: +966 11 2158948 Fax: +966 11 2157910 Email: librarian@alfaisal.edu