artilleryio/artillery

AMQP support

Open

#50 opened on Feb 8, 2016

View on GitHub
 (2 comments) (6 reactions) (0 assignees)JavaScript (7,057 stars) (504 forks)batch import
enhancementhelp wanted

Description

We should add an AMQP engine to make Artillery even more useful for teams working on microservice-oriented architectures where RabbitMQ is often employed as microservice glue.

The existing WebSocket engine (engine_ws.js) would be a good starting point.

Contributor guide

Tech stack
javascriptnodejs
Domain
backendperformance
Issue type
feature
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
3-5 days
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
stale
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
mostly clear
Prerequisites
Node.jsRabbitMQ/AMQP basicsArtillery internals
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
30
Research direction
Explore the existing WebSocket engine at https://github.com/shoreditch ops/artillery core/blob/master/lib/engine ws.js as a template. Understand the engine interface and lifecycle (e.g., createScenario, step). Then implement an AMQP counterpart using a library like amqplib. Consider supporting message exchange patterns (direct, topic) and configuration options. Refer to Artillery's plugin architecture to register the new engine.