Search icon CANCEL
Subscription
0
Cart icon
Your Cart (0 item)
Close icon
You have no products in your basket yet
Arrow left icon
Explore Products
Best Sellers
New Releases
Books
Videos
Audiobooks
Learning Hub
Free Learning
Arrow right icon
Arrow up icon
GO TO TOP
Multi-Cloud Strategy for Cloud Architects

You're reading from   Multi-Cloud Strategy for Cloud Architects Learn how to adopt and manage public clouds by leveraging BaseOps, FinOps, and DevSecOps

Arrow left icon
Product type Paperback
Published in Apr 2023
Publisher Packt
ISBN-13 9781804616734
Length 470 pages
Edition 2nd Edition
Tools
Arrow right icon
Author (1):
Arrow left icon
Jeroen Mulder Jeroen Mulder
Author Profile Icon Jeroen Mulder
Jeroen Mulder
Arrow right icon
View More author details
Toc

Table of Contents (23) Chapters Close

Preface 1. Introduction to Multi-Cloud FREE CHAPTER 2. Collecting Business Requirements 3. Starting the Multi-Cloud Journey 4. Service Designs for Multi-Cloud 5. Managing the Enterprise Cloud Architecture 6. Controlling the Foundation Using Well-Architected Frameworks 7. Designing Applications for Multi-Cloud 8. Creating a Foundation for Data Platforms 9. Creating a Foundation for IoT 10. Managing Costs with FinOps 11. Maturing FinOps 12. Cost Modeling in the Cloud 13. Implementing DevSecOps 14. Defining Security Policies 15. Implementing Identity and Access Management 16. Defining Security Policies for Data 17. Implementing and Integrating Security Monitoring 18. Developing for Multi-Cloud with DevOps and DevSecOps 19. Introducing AIOps and GreenOps in Multi-Cloud 20. Conclusion: The Future of Multi-Cloud 21. Other Books You May Enjoy
22. Index

Introducing DevOps and CI/CD

Before we get into the principles of DevSecOps, we need to have a good understanding of DevOps. There are a lot of views on DevOps, but this book sticks to the definition and principles as defined by the DevOps Agile Skills Association (DASA). It defines a DevOps framework based on six principles:

  • Customer-centric action: Develop an application with the customer in mind: what do they need and what does the customer expect in terms of functionality? This is also the goal of another concept, domain-driven design, which contains good practices for designing.
  • Create with the end in mind: How will the application look when it’s completely finished?
  • End-to-end responsibility: Teams need to be motivated and enabled to take responsibility from the start to the finish of the application life cycle. This results in mottos such as you build it, you run it and you break it, you fix it. One more...
lock icon The rest of the chapter is locked
Register for a free Packt account to unlock a world of extra content!
A free Packt account unlocks extra newsletters, articles, discounted offers, and much more. Start advancing your knowledge today.
Unlock this book and the full library FREE for 7 days
Get unlimited access to 7000+ expert-authored eBooks and videos courses covering every tech area you can think of
Renews at $19.99/month. Cancel anytime
Banner background image