Using Clobbr to quickly load test the ScreenshotOne API
I needed a simple app to quickly grasp the performance of my API. I found a perfect one that suits well for local development and allows you to quickly check your API performance—Clobbr. I and Dan want to share a few thoughts about the load testing and Clobbr.
Historically, API load testing was viewed as an “enterprise” endeavour. The pedigree shows this clearly. jMeter, one of the most popular load testing tools is written in Java – a language that has powered enterprise servers for almost 3 decades.
As software development evolved, APIs have become critical parts of software small to big. Perhaps pushed by microservices and serverless, APIs are now not only an enterprise topic. However, tools regarding API load testing have yet to catch up. They are complicated, heavy, require a lot of configuration and above all – are priced for enterprise use cases.
Understanding Small Companies' API Testing Needs
Small companies and solo developers often operate with limited budgets and resources, which presents different challenges when it comes to API testing. For example:
- Budget constraints
- Simpler Use Cases
- Ease of Use
- Quick and Cost-Effective Results
The tools needed to check all these points are not the goliaths of load testing. Satisfying these requires a focused, ease-to-use and intuitive type of software. To move quickly, no code or servers should be necessary. Moreover, their use cases are a lot simpler. The traditional tools will throw them into terms, features and workflows they don’t need. Those extensive features get in the way and cost a pretty penny.
Lastly, smaller companies may have limited technical expertise or dedicated QA teams. Therefore, an API testing tool should be user-friendly and accessible to non-technical users.
Ease of use is crucial for smaller companies to efficiently set up and run API tests without the need for extensive training or technical know-how. You should be able to jump in and have your first test ready within minutes, without looking up documentation or guides.
Clobbr - Affordable API Testing for Small Companies & Solo Developers
Here’s where Clobbr comes in. There are a few things that make this an indispensable tool.
Clobbr stands out as a unique tool for small companies primarily due to its straightforward and budget-friendly pricing model. Unlike many other API testing tools that follow a subscription-based approach, Clobbr adopts a one-time payment model. This single purchase grants users full access to the tool’s features without any ongoing financial commitment.
Simplicity and good UX
Clobbr boasts an intuitive interface that minimizes the learning curve. Users can easily navigate the tool without the need for extensive training or technical expertise.
The tool streamlines the API testing workflow, allowing users to make requests to multiple endpoints effortlessly. Configuration options, such as setting request timeouts, headers, and payload, are straightforward and user-friendly.
Privacy. No accounts. No servers.
Clobbr prioritizes data privacy and security, assuring users that all data is stored locally, and no sensitive information is shared with third parties. There is no account needed and no server setup.
Real-Life Benefits: Use Case for ScreenshotOne
It helped me to quickly load test my API and potentially “close” a paying customer for my screenshot API.
They asked me if my API could process 100 requests per second in parallel. There are a lot of ways one can do it. From writing your script to using k6 from Grafana Labs. I needed something simple quickly and it should have had with charts. That’s where Clobbr shines.
Until I build a fully-fledged load-testing CI with an isolated production environment, Clobbr is my quick go-to solution to get a grasp of API performance.
You don’t need to spend hours on a course or break the bank to test your API performance. With a few clicks you’ll get a pretty good idea on how your API is going to do under load.
The cool part about this is that Clobbr also has an open source CLI counterpart, so it’s actually possible to contribute, raise bugs and improve it together with the community.