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


APIs are everywhere. With OpenAPI 3 and REST becoming the well-accepted standard among developers, a significant portion of an enterprise developer’s job consists of creating, publishing, discovering, and consuming APIs.

In an environment with a significant number of developers on disparate teams, this inevitably leads to waste: a significant waste of time, effort, and money.

Developers waste energy reverse-engineering inadequately documented APIs. They waste time identifying the right API. They burn unnecessary cycles figuring out how to make their API widely available.

Once they have an API deployed, there’s a waste of time and energy making sure the API is adequately secured and that it’s shared across a large organization, not to mention making sure those APIs are maintained and kept up to date.

Architects may spend undue time building out a central clearing house for discovering APIs and a central gateway for deploying them.