Why should you care?

AwsVerse banking platform isolates payments, accounts, and notifications so teams deploy without monolith releases.

See it live — copy this example

Run in AWS CloudShell / local AWS CLI v2, or follow the matching steps in the AWS Console (Free Tier).

aws ecs create-service \
  --cluster awsverse-prod \
  --service-name payments-api \
  --task-definition payments-api:12 \
  --desired-count 3 \
  --launch-type FARGATE \
  --network-configuration 'awsvpcConfiguration={subnets=[subnet-1a,subnet-1b],securityGroups=[sg-payments]}' \
  --load-balancers 'targetGroupArn=arn:aws:elasticloadbalancing:...:targetgroup/payments/abc,containerName=payments,containerPort=8080'

What happened?

• ECS service runs three Fargate tasks behind ALB target group.
• Each microservice gets own repo, pipeline, and database.

Practice next

1. Split monolith by bounded context.
2. One ECR repo and ECS service per service.
3. Use SQS between services for async ops.
4. Add service mesh (App Mesh) for mTLS.
5. Extract read model to DynamoDB for queries.

Remember

One service one team one deploy. Async messaging reduces coupling. Database per service when possible.

AwsVerse payment service

Payments team ships weekly; ERP monthly.

Outcome: Independent ECS service deploys without touching account service.