0

A development Meteor app runs in a docker container on aws cloud, it accepts user input and makes HTTP requests to 3rd party websites, parses the data and sends back to the user. Apology; my limited understanding of the technology is reflected in the following question.

Since there might be 200+ users thus 200+ requests to 3rd party websites, what best structure to setup the app/container in order that requests from the container to the 3rd party websites is not queued?

Any idea on the bigger picture is much appreciated.

Improve this question

1 Answer 1

Reset to default
0

Scientific method is your friend.

  1. Ask a question:

How will my site perform under various workloads ?

  1. Devise an experiment.

    • Create a way to mimic your users either singly or in groups (I can't offer any advice here it's not my forté but your other friend google, will, I'm sure help out.)

    • Test your site using the method you devise above, using various different simulated user workloads.

  2. Monitor what happens - gather metrics from your monitoring system.

  3. Analyse the data you have gathered. Understand how your system performs under the various workloads you have applied.

  4. Take action as necessary - reengineer your site based on what you find and go back to 2 if required.

  5. Document your decisions for the people who follow you.

Improve this answer

You must log in to answer this question.

Start asking to get answers

Find the answer to your question by asking.

Ask question

Explore related questions

See similar questions with these tags.