aws-serverless-koa VS artillery

Koa has a Lambda handler package (https://github.com/compwright/aws-serverless-koa), and so you should be able to serve anything that plugs into Koa as a middleware (i.e. apollo-server-koa) through your function handler instead. As for your other question about reasonability, I don't have much to offer without knowing your reasoning behind the stack in the first place as opposed to other potential managed database-GraphQL-combo options like Dgraph (Slash GraphQL) or Hasura Cloud or FaunaDB. If the resolver logic you need can't be handled by one of those services, I might wonder whether a Lambda GraphQL endpoint is the best fit in the first place, but your context could render that concern moot.

Usually, I would let organic users be my load test. However, I am working on a project that has an anticipated load on a new-to-my-team stack, so I'm looking into ways to load test.

I've seen tools like k6 (https://k6.io/), Artillery (https://www.artillery.io), and JMeter (https://jmeter.apache.org/).

I've been using Artillery, but it's hard to visualize the results.

What do you use?

This week was Tracetest’s first-ever Launch Week. We’ve been working on a major integration with Artillery for the last month and our team is beyond excited to share it with you all!

I found a tool for load testing called Artillery. Following this guide I installed Artillery and began research for the test configuration.

This is a great blog post! just taking the opportunity here to comment on this:

> Finally for full scale high fidelity load tests there are relatively few tools out there for browser based load testing.

It exists as of a few months ago and it's fully open source: https://github.com/artilleryio/artillery (I'm the lead dev). You write a Playwright script, then run it in your own AWS account on serverless Fargate and scale it out horizontally as you see fit. Artillery takes care of spinning up and down all of the infra. It will also automatically grab and report Core Web Vitals for you from all those browser sessions, and we just released support for tracing so you can dig into the details of each session if you want to (OpenTelemetry based so works with most vendors- Datadago APM, New Relic etc)

So not to stress test Momento or AWS' Lambda, I wanted to build a small but stable 10-minute workload that hits the Momento Topic API and then let Momento trigger the FunctionURL to run the Lambda code. I wrote a small Artillery config file that ramps up to 20 users and then sustains that for the duration. Again, the script is simple to trigger the work.

Tool Spotlight: Featuring insights on how Artillery and Gitpod can enhance and streamline the benchmarking process.

curl is fantastic. There's also HTTPStat which provides a waterfall visualization on top of curl timings: https://github.com/reorx/httpstat

There's also Skytrace (made by yours truly), which provides timing info as a waterfall visualization inspired by HTTPStat + lots more (syntax highlighting for responses, built-in JMESPath support, command-line assertions and checks etc) - https://github.com/artilleryio/artillery/tree/main/packages/...

https://www.artillery.io/

I know it's an annoying answer, but it depends on your application. The only true way to know is to test it using a load tester like artillery. Measuring performance is a fundamental part of any optimisation (otherwise how do you know?), so it's a great idea to be using tools like this anyway.

For this test I have used artillery.io with the following configuration: