node.js-module | 【完结】node.js 实现模块化源码学习 | Runtime Evironment library

Can somebody tell me please if there is some minimal-impact solution to switch between AWS- and localstack env? Might it be serverless-localstack?

I have a series of node.js- java-ee- and spring-boot services, which are deployed as docker-containers (AWS ecs) and inter-connected via AWS sqs and other AWS services.

I imagined using localstack was like the picture here from localstack.cloud and I would switch a real AWS env with a localstack env without the need to change the application code and - even better: the docker-container. The below schema encouraged me that it might really be as simple as that:

I would just change some options in a docker-compose-file or like manipulating a /etc/hosts file where I replace a set of "real" AWS-URLs by localhost:3456. And that's it.

Isn't there something like this? Do I really have to change every single microservice?

As I start to dive deeper I get more and more confused:

• Most tutorials never describe application level but show some calls with "aws --endpoint-url ..." That's nice, but I guess, my node- or java-service won't call the aws shell command, right?

• On application level this would mean that I have to change code for different environments, replace beans by profile in java and import different ones, wouldn't it? For java this would mean: .withEndpointConfiguration(new EndpointConfiguration("http://localhost:4575", "eu-west-1") For the node.js-module sqs-consumer I saw similar solutions...

  These URL changes could have been done on a more abstract level, couldn't they?

• https://github.com/temyers/serverless-localstack sounds like the above imagined solution but there seems not to be much change and there is a heavy WIP-warning. Any experience with this?

So again - can somebody tell me if there is some easy minimal-impact solution to switch between AWS- and localstack env like some sort of "redirect"?

Thanks a lot in advance!