Major security related issues were disclosed just a few days ago affecting CPUs across all vendors and architectures, including Intel and AMD. These vulnerabilities have become known as Meltdown and Spectre and are very severe.
Mitigations have been released for many systems and environment, but you should check if you are fully patched up before continue reading this article! The problem effects all systems, regardless of virtualization or not.
“AWS Well-Architected Framework” is a guideline for review and improvement on
cloud-based architectures. Amazon Web Services recommends “general design
principles” and describes best practice examples.
In this blog posting we sum up some advices on performance testing.
The last part of our blog posting series "Why Load and Performance Testing in the Cloud?" will give an answer to the question "what is the difference in all this to pre-cloud times?". The article is based upon a talk I gave at the AWS PopUp Loft in Berlin.
The second part of our blog posting series shows an overview on the different types of performance testing. Learn more about load testing, scalability testing, stress, spike and soak testing, configuration testing as well as availability and resilience testing. The article is based upon a talk I gave at the AWS PopUp Loft, DevOpsCon 2016 and other occasions.
At the AWS PopUp Loft in Berlin I gave a talk on why load and performance testing is still (or especially) relevant in the era of cloud infrastructure. I expanded the talk for AWS Summit Berlin 2016 and again at DevOpsCon 2016. Here in our blog you will find it in three crunchy bites, beginning with performance and scalability and the importance of performance testing in the cloud era. I will give an overview on the different types of testing and explain the differences between pre and post cloud times.