In this blog post we'll look at Artillery's hybrid workload model, whether it suffers from coordinated omission (**tldr: it doesn't**), and why neither closed nor open models are very suitable for testing most real-world systems
At Artillery we believe that you should load test in production. It's not rocket science, its dangers can be mitigated, and the benefits are worth a bit of extra work
We designed Artillery to be easy to extend and customize through a variety of extension APIs. Artillery comes with batteries included and many out-of-the-box integrations, but every non-trivial load testing project will require at least some customization at some point.
Running load tests at scale can get expensive very quickly, unless you use Artillery. If you're not familiar with Artillery - we do cloud-native load testing.
Say hello to open-source serverless highly-distributed load testing at scale.
