Usage of the new Client() and dealing with high traffic load.

Hey guys, just a quick one - we had some web traffic the other day and it ended up bombing out -

To put in perspective of how the app works, we have a Nuxt Application with Nitro endpoints that handle majority of the Appwrite lookups, it has a shared singleton client, that gets used across database lookups, but yet we still saw a lot of timeout issues, and overloading on to the Appwrite side of things, causing our lookups to fail, even though we lightly cache certain routes for users.

Is there something I'm missing for handling mass amounts of traffic, and are there perhaps some recommended steps to take to get this working as best we can.

We saw things like:

• cause: ConnectTimeoutError: Connect Timeout Error
• ConnectTimeoutError","stack":"ConnectTimeoutError: Connect Timeout Error\n at onConnectTimeout (/app/.output/server/node_modules/node-fetch-native-with-agent/dist/shared/node-fetch-native-with-agent.df7e6bd6.cjs:1:43536)\n at /app/.output/server/node_modules/node-fetch-native-with-agent/dist/shared/node-fetch-native-with-agent.df7e6bd6.cjs:1:42805\n at Immediate._onImmediate (/app/.output/server/node_modules/node-fetch-native-with-agent/dist/shared/node-fetch-native-with-agent.df7e6bd6.cjs:1:43220)\n at process.processImmediate (node:internal/timers:504:21)
• a multitude of fetch errors/failed etc.

Our Appwrite is running on a well spec’d bare metal server, and we have Cloudflare infront of it.

But when a mere 100 users all hit the app at the same time for an event going live at a certain time, we saw all these issues come in and bottleneck the app.

Any suggestions, ideas, etc are all welcome!