Ask HN: Solid setup for local microservices architecture | Hacker News Reader

Ask HN: Solid setup for local microservices architecture

5 pointskostarelo3 comments

What are some impressive setups you've seen or you've implemented on locally replicating a microservices architecture with local DBs and other backend dependencies.

I'm looking into docker-compose with remote docker-compose yaml files but I'm not sure of how solid is going to be.

Our services are mostly Node.js based services and dockerised already. Production environment is setup on AWS ECS.

View on HN

The AWS ECS cli understands the syntax of docker-compose files, so you can use almost the same setup as local development. Also depending on your setup, e.g. if your services are stateless and the state is kept somewhere else like SQS queue, you can parallelize 100x with a single command.

  ecs-cli compose -f docker-compose.prod.yml --ecs-params ecs-params.yml service up --cluster YOUR_CLUSTER

  ecs-cli compose -f docker-compose.prod.yml --ecs-params ecs-params.yml service scale 100 --cluster YOUR_CLUSTER

Not sure if that is what you meant, feel free to get in touch.

Author here: just wanted to clarify that the question was meant to be for creating a local development environment.

why docker-compose and not kubernetes?

Reply on news.ycombinator.com