Skip to content

Service Types

Efe Karakus edited this page Jun 29, 2020 · 4 revisions

Copilot provides various well-architected service architectures for you to quickly go live!

Load Balanced Web Service

An internet-facing service that's behind a load balancer, orchestrated by Amazon ECS on AWS Fargate.

Why

  • Public. Any application that needs to accept traffic from the public internet to perform an operation.

Common use-cases

  • Website. Rendering a server-side website.
  • Public API. A "front-end" API app that fans-out to other backend applications.

Architecture

lb-web-app

Backend Service

A service that's not reachable from the internet, but can be reached with service discovery from your other services.

Why

  • Privacy. If your services are always accessible publicly, then you need to duplicate your authentication and authorization mechanisms across services. You can remove this duplication by keeping your services private and moving the auth mechanisms into a single “frontend” load balanced web service that forwards requests to your backend services.
  • Encapsulation. If you need to migrate a service to a new major version, then a backend service will allow you to seamless migrate traffic from your "frontend" service to the new version.

Common use-cases

  • APIs. Any internal API service.

Architecture

Screen Shot 2020-04-06 at 4 44 19 PM

Clone this wiki locally