<p>I am having trouble testing my application locally, due to my machine having memory constraints.</p>

<p>My application utilizes about 10 different microservices where each service has shared/non-shared AWS resources. Up until now, I've been using <code>localstack</code> to deploy all required AWS mock services and docker to spin up the other dependent microservices. However, I think the overall system has gotten too large for my machine to handle. The only option I could think of is to leverage kubernetes then deploying everything to AWS for testing. I'm hesitant on doing so, as I don't want to spend money on a volunteer project.</p>

<p>Are there any other options to achieve this? Or should I just bite the bullet and pay on-demand?
Thanks in advance.</p>

<blockquote>
  <p>I think the overall system has gotten too large for my machine to handle. The only option I could think of is to leverage kubernetes then deploying everything to AWS for testing</p>
</blockquote>

<p>You have problems running 10 services locally, so you wanna add one more service to make it work? Math says it won't help :-)</p>

<blockquote>
  <p>How to test AWS resources locally with constraints</p>
</blockquote>

<p>There is no need to run all services you have locally.<br>
Each service should have a contract. Services collaborate assumes contracts of each other.<br>
It's enough to run a service assuming contracts of other services without running them in fact.<br>
If all services are mixed together without strong contracts, then there are much bigger problems and super powerful machine only hides them.</p>

<blockquote>
  <p>Or should I just bite the bullet and pay on-demand?</p>
</blockquote>

<p>If you need to test all services together end to end, then it makes sense to test them on production like environment. If it's AWS, then use AWS. If it's on premise systems, then use the same.</p>

<p>And the last thing - let's separate concerns. Kubernetes (and Agile, Docker, DevOps and other buzzwords) doesn't relate here at all. At least assuming current state of the problem.</p>
