Osoby które kupowały "97 Things Every Cloud Engineer Should Know", wybierały także:

• Windows Media Center. Domowe centrum rozrywki 66,67 zÅ‚, (8,00 zÅ‚ -88%)
• Przywództwo w Å›wiecie VUCA. Jak być skutecznym liderem w niepewnym Å›rodowisku 58,64 zÅ‚, (12,90 zÅ‚ -78%)
• Mapa Agile & Scrum. Jak si 57,69 zÅ‚, (15,00 zÅ‚ -74%)
• Sztuka podst 53,46 zÅ‚, (13,90 zÅ‚ -74%)
• Lean dla bystrzaków. Wydanie II 49,62 zÅ‚, (12,90 zÅ‚ -74%)

Spis treści

97 Things Every Cloud Engineer Should Know eBook -- spis treści

• Preface
  • OReilly Online Learning
  • How to Contact Us
• I. Fundamentals
• 1. What Is the Cloud?
  • Nathen Harvey
• 2. Why the Cloud?
  • Nathen Harvey
    • Understand the Role of Technology
    • Automate the Cloud
    • Measure Progress
    • Getting Started > Getting Finished
• 3. Three Keys to Making the Right Multicloud Decisions
  • Brendan OLeary
• 4. Use Managed ServicesPlease
  • Dan Moore
• 5. Cloud for Good Should Be Your Next Project
  • Delali Dzirasa
• 6. A Cloud Computing Vocabulary
  • Jonathan Buck
• 7. Why Every Engineer Should Be a Cloud Engineer
  • Michelle Brenner
• 8. Managing Up: Engaging with Executives on the Cloud
  • Reza Salari
• II. Architecture
• 9. The Future of Containers: Whats Next?
  • Chris Hickman
    • MicroVMs
    • Unikernels
    • So, Whats Next?
• 10. Understanding Scalability
  • Duncan Mackenzie
    • Scaling Options
      • Scaling Up
      • Scaling Out
    • Keep Scalability in Mind, but Dont Overdo It
• 11. Dont Think of Services, Think of Capabilities
  • Haishi Bai
• 12. You Can Cloudify Your Monolith
  • Jake Echanove
• 13. Integrating Microservices in Cloud Native Architecture
  • Kasun Indrasiri
• 14. Containers Arent Magic
  • Katie McLaughlin
• 15. Your CIO Wants to Replatform Only Once
  • Kendall Miller
• 16. Practice Visualizing Distributed Systems
  • Kim Schlesinger
• 17. Know Where to Scale
  • Lisa Huynh
    • Vertical Scaling
    • Horizontal Scaling
    • Conclusion
• 18. Serverless Bad Practices
  • Manasés Jesús Galindo Bello
    • Deploying a Lot of Functions
    • Calling a Function Synchronously
    • Calling a Function Asynchronously
    • Employing Many Libraries
    • Using Many Technologies
    • Not Documenting Functions
• 19. Getting Started with AWS Lambda
  • Marko Sluga
    • Building an Event Handler and Testing the Lambda Function
• 20. Its OK if Youre Not Running Kubernetes
  • Mattias Geniar
    • The Media Tells Us Only Half the Truth
    • Theres Still Much to Improve on the Old and Boring Side of Technology
    • But Dont Sit Still
• 21. Know Thy Topology
  • Nikhil Nanivadekar
    • Modularity
    • Deployment Strategy
    • Datacenter Affinity
• 22. System Fundamentals Will Still Bite You
  • Noah Abrahams
• 23. Cloud Processing Is Not About Speed
  • Rustem Feyzkhanov
• 24. How Serverless Simplifies the Developer Experience
  • Wietse Venema
• III. Migration
• 25. People Will Expect ThingsHelp Them Expect Right
  • Dave Stanke
• 26. Failing a Cloud Migration
  • Lee Atchison
    • Mistake 1: Not Optimizing for the Cloud
    • Mistake 2: Lack of Architectural Strategy
• 27. Optimizing Processes for the Cloud: Patterns and Antipatterns
  • Mike Kavis
    • Antipattern 1: The Wild West
    • Antipattern 2: Command and Control
    • Avoiding Antipatterns
• 28. Why the Lift-and-Shift Model Is Unlikely to Succeed
  • Mike Silverman
• IV. Security and Compliance
• 29. Security at Cloud Native Speed
  • Chris Short
    • Struggles
    • Velocity
    • Continuous Security
    • Platform Security
    • Speed Makes Us Safer
• 30. Essentials of Modern Cloud Governance
  • Derek Martin
    • Subscriptions Matter
    • The Network Has to Come First
    • Security Is Essential
    • Automation Is Required
• 31. Know Where the Secrets Are Kept and How
  • Emmanuel Apau
    • How Do We Share Secrets Between the Infrastructure and the Applications?
    • How Do We Audit Our Secrets?
    • How Do We Share Secrets Among Users?
    • Best Practices
• 32. Dont SSH into Production
  • Fernando Duran
• 33. Identity and Access Management in Cloud Computing
  • Isuru J. Ranawaka
• 34. Treat Your Cloud Environment as if It Were On Premises
  • Iyana Garry
• 35. You Cant Get Information Security Right Without Getting Identity Right
  • Sarah Cecchetti
• 36. Why Are Good AWS Security Policies So Difficult?
  • Stephen Kuenzli
    • The AWS Security Model Is Powerful but Complex
    • How Policies Are Evaluated
    • Cloud Deployments Change Rapidly
    • Summary
• 37. Side Channels and Covert Communications in Cloud Environments
  • Will Deane
• V. Operations and Reliability
• 38. When in Doubt, Test It Out
  • Dan Moore
• 39. Never Take a Single Region Dependency
  • Derek Martin
• 40. Test Your Infrastructure with Game Days
  • Fernando Duran
• 41. Improve Your Monitoring with Visualizations and Dashboards
  • Jason Katzer
• 42. REvisiting the Rs of SRE
  • J. Paul Reed
• 43. The Power of Vulnerability
  • Ken Broeren
• 44. The Basics of Service-Level Objectives
  • Kit Merker, Brian Singer, and Alex Nauda
    • What Are SLOs?
    • SLOs: The Cloud Engineers Best Friend
    • Where Do You Start?
• 45. Oh, No: No Logs
  • Laura Santamaria
• 46. Use Checklists to Manage Risk
  • Lisa Huynh
• 47. Everything Is a DNS Problem: How to (Im)prove
  • Michael Friedrich
• 48. Whats the Time?
  • Nikhil Nanivadekar
• 49. Monitor Your Model Dependencies!
  • Ori Cohen
• 50. Theres No Such Thing as a Development Environment
  • Peter McCool
• 51. Incident Analysis and Chaos Engineering: Complementary Practices
  • Ryan Frantz
    • Incident Analysis
      • Pushing Paper
      • Technical Teaching
      • Surfacing Surprise
    • Chaos Engineering
    • Incident Analysis or Chaos Engineering
    • Recouping our Investments
    • A Vision for the Future
• 52. How Should I Organize My AWS Accounts?
  • Stephen Kuenzli
• 53. Resiliency and Scalability Are Key
  • Tidjani Belmansour
• 54. Monitor, You Will
  • Tidjani Belmansour
    • What Is Monitoring and Why Should We Care?
    • Is Monitoring Required Only for Cloud-Based Applications?
    • What Should We Monitor?
    • Monitoring and Dashboarding
    • We Should Design Our Applications for Monitoring from the Start
• 55. Reliable Systems Dont Happen by Accident
  • Zach Thomas
    • The Architecture Diagram Is Also a Map of Failure Modes
    • Asynchronous Communication Is a Friend of Cloud Reliability
    • Exercise Adverse Conditions
• 56. What Is Toil, and Why Are SREs Obsessed with It?
  • Zachary Nickens
• VI. Software Development
• 57. The Cloud Doesnt Care if It Works on Your Machine
  • Alessandro Diaferia
• 58. KISS It
  • Chris Proto
• 59. Maintaining Service Levels with Feature Flags
  • Dawn Parzych
• 60. Working Upstream
  • Eric Sorenson
    • Survey the Landscape
    • Get Internal Approval
    • Join the Community
    • Design First, Then Code
    • Happy Upstreaming!
• 61. Do More with Less
  • Ivan Krnić
• 62. Everything Is Just Ones and Zeros
  • Lukas Ruebbelke
• 63. Be Prepared to Repeat
  • Ricardo Miranda
    • Strategies to Cope with Duplicate Messages
    • Stateless Consumers
    • Keeping State
    • Conclusions
• 64. Your Greatest Products Are Not the Applications and Services You Produce
  • Ryan Bell
• 65. Avoid Big Rewrites
  • Simon Aronsson
    • Step 1: Be Realistic
    • Step 2: Utilize the Strangler Pattern
    • Step 3: Repeat
• 66. Lean QA: The QA Evolving in the DevOps World
  • Theresa Neate
    • Beware the Cargo Cult
    • Waste
    • QA Is Feedback
    • Early Feedback
    • Lean QA
• 67. Source Code Management for Software Delivery
  • Tiffany Jachja
    • Understanding Version Control
    • What Is Git?
• VII. Cloud Economics and Measuring Spend
• 68. FinOps: How Cloud Finance Management Can Save Your Cloud Program from Extinction
  • Deepak Ramchandani Vensi
    • What Is FinOps?
    • How Do You Get Started with FinOps?
    • Summary
• 69. How Economies of Scale Work in the Cloud
  • Jon Moore
• 70. Managing Network Transit Costs in the Cloud
  • Ken Corless
• 71. Managing the Cloud Migration Cost Spike
  • Manjeet Dadyala
• 72. Damn It, Jim! Im a Cloud Engineer, Not an Accountant!
  • Michael Winslow
• 73. Effectively Monitoring Cloud Services Requires Planning
  • Scott Pantall
• VIII. Automation
• 74. Principles, Patterns, and Practices for Effective Infrastructure as Code
  • Adarsh Shah
    • Key Principles
    • Principles and Practices
• 75. Red, Green, Refactor for Infrastructure
  • Annie Hedgpeth
• 76. Automate or Not-o-Mate?
  • Judy Johnson
• 77. Beyond the Portal: Manage Your Cloud with the CLI
  • Marcello Marrocos
• 78. Treat Your Infrastructure like Software
  • Zachary Nickens
• IX. Data
• 79. So You Want to Migrate Oracle Database into AWS Cloud?
  • Asha Kalburgi
    • Migration of Database
    • Helpful Tools
• 80. DataOps: DevOps for Data Management
  • Banjo Obayomi
    • Reproducible Data
    • Analytics as Code
    • Data as a Platform
• 81. Data Gravity: The Importance of Data Management in the Cloud
  • Geoff Hughes
    • Data Availability
    • Disaster Recovery
    • Data Retention
    • Data Gravity
• X. Networking
• 82. Even in the Cloud, the Network Is the Foundation
  • David Murray
• 83. Networking First
  • Derek Martin
• 84. Handling Network Failures in the Cloud
  • Shayon Mukherjee
• XI. Organizational Culture
• 85. Silos by Any Other Name
  • Brittany Woods
• 86. Focus on Your Team, Not on the Cost
  • Guillaume Blaquiere
• 87. Cloud Engineering Is About Culture, Not Containers
  • Holly Cummins
• 88. The Importance of Keeping Working Systems Working
  • Jan UrbaÅ„ski
• 89. Effectively Navigating Organizational Politics
  • Joshua Zimmerman
    • Delegation
    • Committees
    • Soft Decisions
• 90. The Cloud Is Not About the Cloud
  • Ken Corless
• 91. The Cloud Is Bigger than IT: Enterprise-Wide Training Strategies
  • Mike Kavis
• 92. Systems Thinking and the Support Pager
  • Theresa Neate
    • There Are Always Consequences
    • Systems Thinking in Teams
    • Systems Thinking in Application Support
    • It All Dovetails
• 93. Curating a DevOps Culture and Experience
  • Tiffany Jachja
    • Define Your Target Outcomes
    • Safe Environments
    • Architect Your Technology
• XII. Personal and Professional Development
• 94. Read the DocumentationThen Reread It
  • Jennine Townsend
• 95. Stay Curious
  • Laziz Turakulov
• 96. Empathy as Code
  • Nirmal Mehta
    • Empathy as Code
    • A Sampling of Decision-Making Techniques
• 97. From Zero to Cloud Engineer in Less Than a Year
  • Rachel Sweeney
• Contributors
  • Adarsh Shah
  • Alessandro Diaferia
  • Alex Nauda
  • Annie Hedgpeth
  • Asha Kalburgi
  • Banjo Obayomi
  • Brendan OLeary
  • Brian Singer
  • Brittany Woods
  • Chris Hickman
  • Chris Proto
  • Chris Short
  • Dan Moore
  • Dave Stanke
  • David Murray
  • Dawn Parzych
  • Deepak Ramchandani Vensi
  • Delali Dzirasa
  • Derek Martin
  • Duncan Mackenzie
  • Emily Freeman
  • Emmanuel Apau
  • Eric Sorenson
  • Fernando Duran
  • Geoff Hughes
  • Guillaume Blaquiere
  • Haishi Bai
  • Holly Cummins
  • Isuru J. Ranawaka
  • Ivan Krnić
  • Iyana Garry
  • J. Paul Reed
  • Jake Echanove
  • Jan UrbaÅ„ski
  • Jason Katzer
  • Jennine Townsend
  • Jon Moore
  • Jonathan Buck
  • Joshua Zimmerman
  • Judy Johnson
  • Kasun Indrasiri
  • Katie McLaughlin
  • Ken Broeren
  • Ken Corless
  • Kendall Miller
  • Kim Schlesinger
  • Kit Merker
  • Laura Santamaria
  • Laziz Turakulov
  • Lee Atchison
  • Lisa Huynh
  • Lukas Ruebbelke
  • Manasés Jesús Galindo Bello
  • Manjeet Dadyala
  • Marcello Marrocos
  • Marko Sluga
  • Mattias Geniar
  • Michael Friedrich
  • Michael Winslow
  • Michelle Brenner
  • Mike Kavis
  • Mike Silverman
  • Nathen Harvey
  • Nikhil Nanivadekar
  • Nirmal Mehta
  • Noah Abrahams
  • Ori Cohen
  • Peter McCool
  • Rachel Sweeney
  • Reza Salari
  • Ricardo Miranda
  • Rustem Feyzkhanov
  • Ryan Bell
  • Ryan Frantz
  • Sarah Cecchetti
  • Scott Pantall
  • Shayon Mukherjee
  • Simon Aronsson
  • Stephen Kuenzli
  • Theresa Neate
  • Tidjani Belmansour
  • Tiffany Jachja
  • Wietse Venema
  • Will Deane
  • Zach Thomas
  • Zachary Nickens
• Index