You're reading from DevSecOps in Practice with VMware Tanzu Build, run, and manage secure multi-cloud apps at scale on Kubernetes with the Tanzu portfolio

Product type Paperback

Published in Jan 2023

Publisher Packt

ISBN-13 9781803241340

Length 436 pages

Edition 1st Edition

Tools

Kubernetes

Concepts

DevOps

Authors (2):

Robert Hardt

Parth Pandit

View More author details

Table of Contents (19) Chapters

Preface

1. Part 1 – Building Cloud-Native Applications on the Tanzu Platform

2. Chapter 1: Understanding the Need to Move to a Cloud Platform FREE CHAPTER

3. Chapter 2: Developing Cloud-Native Applications

4. Chapter 3: Building Secure Container Images with Build Service

5. Chapter 4: Provisioning Backing Services for Applications

6. Chapter 5: Defining and Managing Business APIs

7. Part 2 – Running Cloud-Native Applications on Tanzu

8. Chapter 6: Managing Container Images with Harbor

9. Chapter 7: Orchestrating Containers across Clouds with Tanzu Kubernetes Grid

10. Chapter 8: Enhancing Developer Productivity with Tanzu Application Platform

11. Part 3 – Managing Modern Applications on the Tanzu Platform

12. Chapter 9: Managing and Controlling Kubernetes Clusters with Tanzu Mission Control

13. Chapter 10: Realizing Full-Stack Visibility with VMware Aria Operations for Applications

14. Chapter 11: Enabling Secure Inter-Service Communication with Tanzu Service Mesh

15. Chapter 12: Bringing It All Together

16. Index

Why subscribe?

17. Other Books You May Enjoy

Appendix

Summary

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.

Finally...