Book description
If you create, manage, operate, or configure systems running in the cloud, you're a cloud engineer--even if you work as a system administrator, software developer, data scientist, or site reliability engineer. With this book, professionals from around the world provide valuable insight into today's cloud engineering role.
These concise articles explore the entire cloud computing experience, including fundamentals, architecture, and migration. You'll delve into security and compliance, operations and reliability, and software development. And examine networking, organizational culture, and more. You're sure to find 1, 2, or 97 things that inspire you to dig deeper and expand your own career.
- "Three Keys to Making the Right Multicloud Decisions," Brendan O'Leary
- "Serverless Bad Practices," Manases Jesus Galindo Bello
- "Failing a Cloud Migration," Lee Atchison
- "Treat Your Cloud Environment as If It Were On Premises," Iyana Garry
- "What Is Toil, and Why Are SREs Obsessed with It?", Zachary Nickens
- "Lean QA: The QA Evolving in the DevOps World," Theresa Neate
- "How Economies of Scale Work in the Cloud," Jon Moore
- "The Cloud Is Not About the Cloud," Ken Corless
- "Data Gravity: The Importance of Data Management in the Cloud," Geoff Hughes
- "Even in the Cloud, the Network Is the Foundation," David Murray
- "Cloud Engineering Is About Culture, Not Containers," Holly Cummins
Publisher resources
Table of contents
- Preface
- I. Fundamentals
- 1. What Is the Cloud?
- 2. Why the Cloud?
- 3. Three Keys to Making the Right Multicloud Decisions
- 4. Use Managed Services—Please
- 5. Cloud for Good Should Be Your Next Project
- 6. A Cloud Computing Vocabulary
- 7. Why Every Engineer Should Be a Cloud Engineer
- 8. Managing Up: Engaging with Executives on the Cloud
- II. Architecture
- 9. The Future of Containers: What’s Next?
- 10. Understanding Scalability
- 11. Don’t Think of Services, Think of Capabilities
- 12. You Can Cloudify Your Monolith
- 13. Integrating Microservices in Cloud Native Architecture
- 14. Containers Aren’t Magic
- 15. Your CIO Wants to Replatform Only Once
- 16. Practice Visualizing Distributed Systems
- 17. Know Where to Scale
- 18. Serverless Bad Practices
- 19. Getting Started with AWS Lambda
- 20. It’s OK if You’re Not Running Kubernetes
- 21. Know Thy Topology
- 22. System Fundamentals Will Still Bite You
- 23. Cloud Processing Is Not About Speed
- 24. How Serverless Simplifies the Developer Experience
- III. Migration
- 25. People Will Expect Things—Help Them Expect Right
- 26. Failing a Cloud Migration
- 27. Optimizing Processes for the Cloud: Patterns and Antipatterns
- 28. Why the Lift-and-Shift Model Is Unlikely to Succeed
- IV. Security and Compliance
- 29. Security at Cloud Native Speed
- 30. Essentials of Modern Cloud Governance
- 31. Know Where the Secrets Are Kept and How
- 32. Don’t SSH into Production
- 33. Identity and Access Management in Cloud Computing
- 34. Treat Your Cloud Environment as if It Were On Premises
- 35. You Can’t Get Information Security Right Without Getting Identity Right
- 36. Why Are Good AWS Security Policies So Difficult?
- 37. Side Channels and Covert Communications in Cloud Environments
- V. Operations and Reliability
- 38. When in Doubt, Test It Out
- 39. Never Take a Single Region Dependency
- 40. Test Your Infrastructure with Game Days
- 41. Improve Your Monitoring with Visualizations and Dashboards
- 42. REvisiting the Rs of SRE
- 43. The Power of Vulnerability
- 44. The Basics of Service-Level Objectives
- 45. Oh, No: No Logs
- 46. Use Checklists to Manage Risk
- 47. Everything Is a DNS Problem: How to (Im)prove
- 48. What’s the Time?
- 49. Monitor Your Model Dependencies!
- 50. There’s No Such Thing as a Development Environment
- 51. Incident Analysis and Chaos Engineering: Complementary Practices
- 52. How Should I Organize My AWS Accounts?
- 53. Resiliency and Scalability Are Key
- 54. Monitor, You Will
- 55. Reliable Systems Don’t Happen by Accident
- 56. What Is Toil, and Why Are SREs Obsessed with It?
- VI. Software Development
- 57. The Cloud Doesn’t Care if It Works on Your Machine
- 58. KISS It
- 59. Maintaining Service Levels with Feature Flags
- 60. Working Upstream
- 61. Do More with Less
- 62. Everything Is Just Ones and Zeros
- 63. Be Prepared to Repeat
- 64. Your Greatest Products Are Not the Applications and Services You Produce
- 65. Avoid Big Rewrites
- 66. Lean QA: The QA Evolving in the DevOps World
- 67. Source Code Management for Software Delivery
- VII. Cloud Economics and Measuring Spend
- 68. FinOps: How Cloud Finance Management Can Save Your Cloud Program from Extinction
- 69. How Economies of Scale Work in the Cloud
- 70. Managing Network Transit Costs in the Cloud
- 71. Managing the Cloud Migration Cost Spike
- 72. Damn It, Jim! I’m a Cloud Engineer, Not an Accountant!
- 73. Effectively Monitoring Cloud Services Requires Planning
- VIII. Automation
- 74. Principles, Patterns, and Practices for Effective Infrastructure as Code
- 75. Red, Green, Refactor for Infrastructure
- 76. Automate or Not-o-Mate?
- 77. Beyond the Portal: Manage Your Cloud with the CLI
- 78. Treat Your Infrastructure like Software
- IX. Data
- 79. So You Want to Migrate Oracle Database into AWS Cloud?
- 80. DataOps: DevOps for Data Management
- 81. Data Gravity: The Importance of Data Management in the Cloud
- X. Networking
- 82. Even in the Cloud, the Network Is the Foundation
- 83. Networking First
- 84. Handling Network Failures in the Cloud
- XI. Organizational Culture
- 85. Silos by Any Other Name
- 86. Focus on Your Team, Not on the Cost
- 87. Cloud Engineering Is About Culture, Not Containers
- 88. The Importance of Keeping Working Systems Working
- 89. Effectively Navigating Organizational Politics
- 90. The Cloud Is Not About the Cloud
- 91. The Cloud Is Bigger than IT: Enterprise-Wide Training Strategies
- 92. Systems Thinking and the Support Pager
- 93. Curating a DevOps Culture and Experience
- XII. Personal and Professional Development
- 94. Read the Documentation—Then Reread It
- 95. Stay Curious
- 96. Empathy as Code
- 97. From Zero to Cloud Engineer in Less Than a Year
-
Contributors
- Adarsh Shah
- Alessandro Diaferia
- Alex Nauda
- Annie Hedgpeth
- Asha Kalburgi
- Banjo Obayomi
- Brendan O’Leary
- 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
Product information
- Title: 97 Things Every Cloud Engineer Should Know
- Author(s):
- Release date: December 2020
- Publisher(s): O'Reilly Media, Inc.
- ISBN: 9781492076735
You might also like
book
97 Things Every Data Engineer Should Know
Take advantage of today's sky-high demand for data engineers. With this in-depth book, current and aspiring …
book
97 Things Every Engineering Manager Should Know
Tap into the wisdom of experts to learn what every engineering manager should know. With 97 …
audiobook
Software Architecture: The Hard Parts
There are no easy decisions in software architecture. Instead, there are many hard parts-difficult problems or …
book
Software Architecture: The Hard Parts
There are no easy decisions in software architecture. Instead, there are many hard parts--difficult problems or …