Apigility vs Loader.io: What are the differences?
Apigility: The world's easiest way to create high-quality APIs. An API-based architecture is essential to agile delivery of mobile applications. Apigility provides JSON representations that can be parsed and used in any mobile framework; write for the web or native applications simultaneously!; Loader.io: Simple Cloud-based Load Testing. Loader.io is a free load testing service that allows you to stress test your web-apps/apis with thousands of concurrent connections.
Apigility belongs to "API Tools" category of the tech stack, while Loader.io can be primarily classified under "Load and Performance Testing".
Apigility is an open source tool with 477 GitHub stars and 144 GitHub forks. Here's a link to Apigility's open source repository on GitHub.
What is Apigility?
What is Loader.io?
Need advice about which tool to choose?Ask the StackShare community!
What are the cons of using Apigility?
What are the cons of using Loader.io?
Sign up to get full access to all the companiesMake informed product decisions
Apigility is loyal to the standards; we do not need a framework to write custom REST APIs, anyone can do that; we need a framework that makes sticking with the standards easy.
Every PHP framework should be designed in such a way, that it forces you to think about what you are doing, the current PHP mind-set is too much crowded with lazy documentation of custom-solutions that do not work as expected (because the language gives you too much freedom).
With Apigility it is easy to build RESTful APIs in a declarative way, so that you do not need to write tests for every API Service you create, because the underlying code doesn't change or break, all functionality comes within the framework, that has already been tested.
You do not need to write any boiler plate code, which is huge plus compared to Symfony 2 and the likes.
Apigility has had some reliability problems with newest releases and as far as I know, they do not report which release is the latest stable. But of course, they reached the 1.0 in 2015.
I don’t remember exactly how I heard about Loader.io. I think I was adding load testing services to Leanstack. I saw it was a SendGrid Labs project, so there would be competent people behind it. And since they had a Heroku Add-On it was easy to get started. Loader.io is cool because it’s super simple to set up.
When executing tests, you can see error rate and average response times. But we also check the Heroku logs to see if they are real errors.
My biggest complaint: figuring out what load to set for your tests is difficult. We don’t understand the language they use and no one we’ve spoken to that has used Loader.io understands it either. We’ve been testing at 250 clients (maintain client load) for all of our tests on 2 dynos. That means a constant load of 250 people using the site over a minute, or so I thought. The number of requests at the end of the test suggests it’s more like 250 additional clients hitting the site every second for a minute. But I guess accommodating a higher load is better anyways? 250 concurrent users seems to be our average HN traffic spike so that’s why we went with that load.