Bombard allows you to run sizable and complex scenario load tests with minimal setup. It is easy to use, easy to learn, runs complex scenarios, and has zero maintenance. Bombard wraps Artillery-core in an Aws Lambda script and allows you to easily run load testing from a given number of lambdas.
Bombard focuses on the following:
There are many other great tools out there to do load testing well. If Bombard does not seem right for your use case, take a look at the Related Projects section for a list of a few other tools.
Bombard is motivated and heavily influence by Artillery-Dino (https://github.com/hassy/artillery-dino) by Hassy Veldstra <firstname.lastname@example.org>.
You will need an AWS account. You must have sufficient privileges on your AWS account to Create and Invoke a Lambda Function,
Artillery-Dino - "Dino lets you run large scale load tests from AWS Lambda."
Artillery.io - "Artillery is a modern, powerful & easy-to-use load testing toolkit. Use it to make your applications stay scalable, performant & resilient under high load."
Bees With Machine Guns - "A utility for arming (creating) many bees (micro EC2 instances) to attack (load test) targets (web applications)."
Gatling - "Gatling is an open-source load testing framework based on Scala, Akka and Netty"
JMeter - "The Apache JMeter™ application is open source software, a 100% pure Java application designed to load test functional behavior and measure performance."
ab - "ab is a tool for benchmarking your Apache Hypertext Transfer Protocol (HTTP) server. "
wrk - "wrk is a modern HTTP benchmarking tool capable of generating significant load when run on a single multi-core CPU."
AWS Lambda - "AWS Lambda is a zero-administration compute platform for back-end web developers that runs your code for you in the AWS cloud and provides you with a fine-grained pricing structure."
npm install -g bombard
Deploy the CloudFormation stack:
In a work directory, run
bombard-setup. This will create a
./config.json file with information about your newly created CloudFormation Stack. (Use
bombard-setup -s StackName if you did not use the default stack name.)
If you would like to make changes to the CloudFormation template, do not wish to run the template from the above link, or would like to build your own lambda, use the following steps.
The source for the lambda script can be found in
lambda/src. Build your own lambda by calling
npm run build. The resulting index.js will be in
lambda/lib. The zipped file will be in
If you have build your own lambda, upload the zipped file to an s3 bucket you control. You will need to change the
LambdaZipS3Bucket parameters of the CloudFormation template to point to the new zip file.
Create a CloudFormation Stack using
./CloudFormation/bombard.yaml. This will:
bombard --script script.json -n 1
Note: You will require AWS credentials with permissions to invoke the lambda and to read the SQS queue. This must be run from the same directory as your
See the (Artillery.io guide)[https://artillery.io/docs/basicconcepts.html] for detailed instructions on how to write a test script.
Bombard can take in a csv payload file with the
-p parameter (eg.
-p payload.csv). This payload will be sent to the Lambda along with your script.
secretauth,tt0107290,"best movie ever"secretauth,tt0369610,"worst movie ever"
You can define columns in your csv in your scripts
config section like so:
The Artillery Lambda will select a random row to use for each scenario. They can be used in your script like so:
AWS Lambda has a timeout of 300 seconds. Artillery scripts that last longer than 300 that will behave poorly.
Bombard allows you to essentially perform a distributed denial-of-service attack. If you do not have permission to use Bombard against a service, do not do it. It is unethical and will almost certainly have legal consequences.
You must read and conform to the AWS Acceptable Use Policy.
This project is under MPLv2, see LICENSE.txt.