Chapter 38. When in Doubt, Test It Out
Dan Moore
When I taught AWS certification courses, I’d often get questions about how a service behaved under load or other unusual circumstances. Frequently, I could answer from personal experience or by asking other instructors; occasionally, class members provided their insights. Sometimes I could dig up relevant vendor documentation.
However, my default answer was, “Test it for yourself. There’s no substitute for testing.”
This is one of the great advantages of the cloud. When you have a question about the performance or behavior of a service or system, spin it up and test it. This will cost you money and time configuring the system, but certainly will be cheaper than ordering hardware, racking it, and then also configuring the system. When you’re done with your testing, you can tear down the infrastructure and never worry about it again. This sure beats shipping a server back to the manufacturer.
Of course, no testing scenario can replicate production perfectly. But you can get pretty close (especially if you can reuse production traffic).
When you do test, start by documenting what you want to achieve. What is the question you are trying to answer? Make sure to seek feedback from other team members and/or search online, as it’s possible someone has already answered your question. If you do find answers, ...
Become an O’Reilly member and get unlimited access to this title plus top books and audiobooks from O’Reilly and nearly 200 top publishers, thousands of courses curated by job role, 150+ live events each month,
and much more.
Read now
Unlock full access