Gatling version: 3.14
Gatling flavor: java kotlin scala javascript typescript
Gatling build tool: maven gradle sbt bundle npm
Hi Community,
Has there ever been any appetite to mix protocols somewhat as part of a test?
The idea here being that some applications take an input in one form and an output in another.
e.g. JMS Input, Kafka Output
Or an API based input and a message output (e.g. REST POST / Kafka Event out)
We are looking at load/data testing a service along with running an API (REST / http) based stress test at the same time to observe how the application handles down to the persistence layer for example:
Load X amount of data, whilst running heavy API requests.
Validating throughput / response times of loads.
This may look something like (pseudo somewhat):
scenario(api_test, http, “10 query by ID requests for Ids”, jdbc_feeder (to get Id’s)).duration(1h)
scenario(load_test, jms_in, kafka_events out, “load 100,000 items”).duration(1h)
(Above is for the idea rather than syntactically correct)
results:
api_test RPS etc
load_test RPS etc
I have worked with / made small contributions to GitHub - galax-io/gatling-kafka-plugin: Gatling protocol plugin for supporting Kafka., so understand the protocol / trackers etc. If a sender could generate a key for the tracker and a receiver for the match key, would it be more of a pain to try and use different protocols for send vs (read||receive)?
Thanks in advance for any constructive thoughts on this.
Russ