Need advice about which tool to choose?Ask the StackShare community!
AWS Device Farm vs Gatling: What are the differences?
Developers describe AWS Device Farm as "Test your app on real devices in the AWS Cloud". Run tests across a large selection of physical devices in parallel from various manufacturers with varying hardware, OS versions and form factors. On the other hand, Gatling is detailed as "open-source load testing framework based on Scala, Akka and Netty". Gatling is a highly capable load testing tool. It is designed for ease of use, maintainability and high performance Out of the box, Gatling comes with excellent support of the HTTP protocol that makes it a tool of choice for load testing any HTTP server. As the core engine is actually protocol agnostic, it is perfectly possible to implement support for other protocols. For example, Gatling currently also ships JMS support..
AWS Device Farm and Gatling can be primarily classified as "Load and Performance Testing" tools.
Gatling is an open source tool with 4.3K GitHub stars and 918 GitHub forks. Here's a link to Gatling's open source repository on GitHub.
Streamdata.io, SpectoLabs Ltd, and StellaService are some of the popular companies that use Gatling, whereas AWS Device Farm is used by Getaway GmbH, StaffConnect, and Unscriptd. Gatling has a broader approval, being mentioned in 21 company stacks & 14 developers stacks; compared to AWS Device Farm, which is listed in 5 company stacks and 3 developer stacks.
Pros of AWS Device Farm
- 1000 free minutes3
- Pay as you go pricing2
Pros of Gatling
- Great detailed reports6
- Can run in cluster mode5
- Loadrunner5
- Scala based3
- Load test as code2
- Faster0
Sign up to add or upvote prosMake informed product decisions
Cons of AWS Device Farm
- Records all sessions, blocks on processing when done1
- You need to remember to turn airplane mode off1
Cons of Gatling
- Steep Learning Curve2
- Hard to test non-supported protocols1
- Not distributed0