I am trying to autoscale Meteor using AWS. So it could handle more request simultaneously. Also, the solution should be cheaper compared to other available options.
For example, If we go for AWS t2.Medium instance, then the monthly cost would be around 46$.
So, the hunt starts for getting a cheap and better solution.
I found AWS Beanstalk could be the cheaper option as it could be deployed on t2.micro instance and it also cheaper than t2.medium (Free for the first year).
I configured it correctly, and its working.
It could be creating AMI (Amazon Machine Images i.e Replica of existing) for the current elastic beanstalk Machine and then add a load balancer in it. (Source Ref: Also, the video link for the same functionality is also attached.)As the Database is already separated from the main code and hosted over MLAB, so any other machine con also connects with the Web App.
Also, the Load Balancing could be handled with the NGINX that could be configured on one of the server and load balancings can be handled afterward.
Is this solution would work? Is there the possibility of handing the load balancing and autoscaling this way? If not what would be the best possible way I could achieve this?
Question: As both of the instances are the replica of each other if we change in Nginx for one file & add request forwarding for the other machine then would it also impacting the machine 2. Or Are they separate entity?
It would be great if someone could help on this. I need urgent help on this.