Gatling and Eventual Consistency

Do you have any tips or tricks for testing an eventually consistent system using Gatling? My system is based on CQRS. This means that after creating a new entity via an HTTP POST, it takes some time for the item to become visible through an HTTP GET, due to the propagation of events from the write side to the read side. Are there any ways to make Gatling highlight this eventual consistency in a report?
Thank you and cheers!

  • POST
  • group to measure the duration
    • loop until the change is visible
      • GET
      • loop pause (hence group duration granularity)

But this might generate lots of GET requests and the granularity might be in the same order than what you’re trying to measure :man_shrugging:

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.