This repository was launched using CDK.

Can the whole setup be mirrored using Terraform.

Questions

• Does Terraform have better support for Routes in AppMesh
• Is this simpler with TF
• Can we decouple the container build&push from the infrastructure deploy.

We want to be able to roll out service updates without downtime.
This issue might be dependent on #4

Blue/green deployments would also be really beneficial. How would we leverage healthchecks to roll traffic between old and new versions of a service.

Add GRPC communication between ping and pong

How well does it perform over the mesh?

What happens to a GRPC stream is you alter the routing state of the mesh, e.g. migrate a route to a new virtual node.

Each Fargate service contains just one container at the moment and there is no ALB in front of the service. Do we need to change the architecture, using service level ALB's to create high availability.

Scenarios

• If we scale up the number of containers, is DNS/Cloudmap suitable to manage the balancing of traffic

  • Do CloudMap/Docker/Route53 healthchecks help?

• Similarly does scale in work well. How quickly can envoy pick up changes and route around killed containers?

  • Do CloudMap/Docker/Route53 healthchecks help?

Questions

The ultimate questions to answer here:

• Are ALB's required in front of services for high availability
• How do healthchecks at the various levels help?
• Do SRV records help with these scenarios.

Try deploying the ping pong services to EKS.

Does this provide any benefits when developing locally?

What K8s api's do we have access to to gather metrics?

Can we add support for OpenTracing/OpenCensus collection from the aws envoy sidecar.

Currently envoy doesn't directly support OpenTelemetry - envoyproxy/envoy#9958

Currently the Fargate containers will receive a public IP.

We should put the service behind something more suitable to handle public internet traffic.
We also would like to have a fixed hostname to make requests to.

Suggestions

• API Gateway
• ALB

Can we use the AppMesh managed ingress (virtual gateway) - aws/aws-app-mesh-roadmap#37

This is available in the preview channel.

Make the ping-pong service jazzy!