explaingit

rakyll/boom

★ 4,705GoAudience · ops devopsComplexity · 1/5Setup · easy

TLDR

Boom was an HTTP/HTTPS load testing tool written in Go meant to replace ApacheBench, this repo is abandoned and has moved to a new location under the name 'hey', go there for current usage.

Mindmap

mindmap
  root((boom))
    What it does
      HTTP load testing
      HTTPS benchmarking
      ApacheBench replacement
    Tech stack
      Go
    Status
      Abandoned
      Moved to hey
    Audience
      Developers
      Ops engineers
Click or tap to explore — scroll the page freely

Code map

Detail Auto

An interactive map of this repo's files and how they connect — its source is parsed live in your browser. Click Visualize to build it.

filefunction / class

Things people build with this

USE CASE 1

Use the successor project 'hey' (linked from this repo) to send load to an HTTP or HTTPS endpoint and measure throughput and latency.

USE CASE 2

Migrate any existing scripts or CI jobs that reference 'boom' to the 'hey' repository, which is the actively maintained replacement.

Tech stack

Go

Getting it running

Difficulty · easy Time to first run · 5min

This repository is abandoned, use the 'hey' repository instead, which is the actively maintained successor with the same functionality.

No license information is available in this abandoned repository.

In plain English

Boom was an HTTP and HTTPS load testing tool written in Go, intended as a simpler replacement for ApacheBench, the classic web server benchmarking utility. The repository has been abandoned and the README consists only of a notice saying the project has moved to a different repository under the name "hey." The author also notes a naming conflict with another project called boom and asks users to switch to the new location. No feature documentation, usage instructions, or other details remain in this repository.

Copy-paste prompts

Prompt 1
This repo (boom) has moved to 'hey'. Show me how to install hey and run a load test against my local API server with 200 concurrent workers and 5000 total requests.
Prompt 2
Using the hey tool (the replacement for boom), how do I benchmark an HTTPS endpoint and output results as a latency histogram?
Prompt 3
How do I integrate hey (formerly boom) into a CI pipeline to fail a build if my API's p99 latency exceeds 200ms under load?
Open on GitHub → Explain another repo

← rakyll on gitmyhub — every repo by this author, as a profile.

Verify against the repo before relying on details.