Book Image

DevSecOps in Practice with VMware Tanzu

By : Parth Pandit, Robert Hardt
Book Image

DevSecOps in Practice with VMware Tanzu

By: Parth Pandit, Robert Hardt

Overview of this book

As Kubernetes (or K8s) becomes more prolific, managing large clusters at scale in a multi-cloud environment becomes more challenging – especially from a developer productivity and operational efficiency point of view. DevSecOps in Practice with VMware Tanzu addresses these challenges by automating the delivery of containerized workloads and controlling multi-cloud Kubernetes operations using Tanzu tools. This comprehensive guide begins with an overview of the VMWare Tanzu platform and discusses its tools for building useful and secure applications using the App Accelerator, Build Service, Catalog service, and API portal. Next, you’ll delve into running those applications efficiently at scale with Tanzu Kubernetes Grid and Tanzu Application Platform. As you advance, you’ll find out how to manage these applications, and control, observe, and connect them using Tanzu Mission Control, Tanzu Observability, and Tanzu Service Mesh. Finally, you’ll explore the architecture, capabilities, features, installation, configuration, implementation, and benefits of these services with the help of examples. By the end of this VMware book, you’ll have gained a thorough understanding of the VMWare Tanzu platform and be able to efficiently articulate and solve real-world business problems.
Table of Contents (19 chapters)
Part 1 – Building Cloud-Native Applications on the Tanzu Platform
Part 2 – Running Cloud-Native Applications on Tanzu
Part 3 – Managing Modern Applications on the Tanzu Platform

Enabling Secure Inter-Service Communication with Tanzu Service Mesh

Enterprise software has changed significantly in the last few years. Some of you reading this may remember when most software was written as a single monolith by a small team of developers. The application had to be deployed, updated, started, stopped, and scaled as a single unit.

As software began to evolve in the early to mid-2000s, demands on software and software developers started to grow along four axes:

  • Time to value: Teams were expected to deliver bug fixes, improvements, and new value-delivering features on ever-shrinking timelines.
  • Elasticity: Teams needed to scale “hot” services independently and deploy individual features without having to build, test, and deploy the entire monolith all at once.
  • Fault-tolerance: When an individual service failed or started to degrade, it shouldn’t affect other services, and the system should be able to work around the problematic...