I am currently developing a cloud backup solution which involves upto 8 micro services developed in springboot and using mongo DB atlas as the persistence layer.
The micro services involve a Netflix ZUUL api gateway and netflix Eureka as the service discovery mechanism. The micro services are required to talk to each other obviously.
The micro services are dockerized. So far i have been deploying them to an EC2 instance using a docker compose file listing all the services and communication using docker networking
Now i have been trying to use ECS for deploying the micro services. I have been following the below link to creating the cluster etc. https://docs.aws.amazon.com/AmazonECS/latest/developerguide/ecs-cli-tutorial-ec2.html
My question is as follows
Should i create a task definition per micro service and deploy them to a common cluster or should there be a single task wherein i should have all the micro services coagulated together using the docker compose file? How service discovery work in such a case?
Currently in my applications , the services talk to each other using feign proxy and eureka server. What is the best way to retain it as it is or what do you suggest? I earlier used fargate and deployed the micro services but the service discovery and service registration was failing
Please guide my what is the best way to design the deployment of such an application in ECS