Introducing AWS App Mesh - MAD303 - Santa Clara AWS Summit

© 2019, Amazon Web Services, Inc. orits affiliates. All rights reserved.S UM M I T
Introducing AWS App Mesh
Nick Coult
Principal product manager
AWS
M A D 3 0 3

Agenda
Some whys …
Why a service mesh?
Why App Mesh?
And some hows …
App Mesh constructs
Integrating App Mesh with services
Demo
Roadmap
Partners

App Mesh: Application-level communication across AWS
Communicating between instances
Fixed endpoints at specific addresses
Firewall to allow or block connection attempts
Service discovery
Real-time map of service availability
Applications accept or reject calls

App Mesh works across compute services
Amazon ECS
AWS Fargate
Amazon EKS
Amazon EC2
AWS App Mesh
Kubernetes on EC2

S UM M I T © 2019, Amazon Web Services, Inc. orits affiliates. All rights reserved.
Nitin Mahajan
Executive Director, Service Engineering
Edmunds.com

Our platform
MajorCar Manufacturers
20 MILLION
MonthlyCar Shoppers
10K Dealer
Partners

“Being challenged in life is inevitable, being defeated is optional.”
Roger Crawford

MODERNSOFTWARE
DEVELOPMENT
ARCHITECTURE : MICROSERVICES
SMALL CROSS FUNCTIONAL TEAMS CONTINUOUS DEPLOYMENT

Loosely Coupled & High Cohesion

Business Capability
Subdomain

Node.js
Database
JavaNode.is
Java
Infrastructure team
Product
teams
Platform
teams
Java
Service Teams
Java
Java
Java
Database
Database
Database
Product
teams

Challenges with Microservices
Control Over Service to Service Communication
Visibility into Service to Service Communicationi.e., Observability
Create a culture of innovationby organizing into small DevOps teams
Ensure trust by automating security and compliance

What is needed
Consistentcommunications
management
Complete visibility Failure isolation
and protection
Fine-grained deployment
controls

Why App Mesh?
http/tcp
Service
team A
Service
team B
Common need: Manage inter-service traffic
How to generate uniform logs,
metrics and traces
How to load balance traffic
How to shift traffic between
deployments
How to decouple service teams
How to minimize impact to
application code

Why App Mesh?
http/tcp
Service
team A
Service
team B
Proxy
Sits between all services
Manages and observes traffic
Control plane
Translates intent to proxy config
Distributes proxy config
Control plane

Proxy
Why a side-car proxy?
Configurable: Separates
business logic from operations
Minimizes inconsistencies
Decouples install/upgrade

Side-car proxy with containers
Proxy runs
as a container
Task or pod
External traffic
Application
code

OSS project
Wide community support, numerous integrations
Stable and production-proven
Graduated Project in Cloud Native Computing Foundation
Started at Lyft in 2016
App Mesh uses Envoy Proxy

App Mesh control plane configures every proxy

Logging
HTTP access logging
Amazon CloudWatch Logs
Available as container logs on Amazon
ECS, AmazonEKS,
AWS Fargate
Metrics
CloudWatch metrics
StatsD (with tags)
Prometheus
Tracing
AWS X-Ray
Other Envoy tracing drivers
Application observability

Traffic shaping
Load balancing
Weight targets
Service discovery (DNS + AWS Cloud Map)
Health checks
Retries*
Timeouts*
Circuit breakers*
Routing controls
Protocols support (HTTP, TCP, gRPC*)
Path-based
Header-based*
Cookie-based*
Host-based*
*Coming soon
Client-side traffic management

Today, App Mesh is generally available worldwide
Observability and traffic control
Easily export logs, metrics, and traces
Client-side load balancing, routing
AWS container services compatibility
Amazon Elastic Container Service (AmazonECS)
Amazon Elastic Container Service for Kubernetes (Amazon EKS)
AWS Fargate
EC2 compatibility
Integrate with services running directly on EC2 instances

App Mesh constructs
Mesh
Virtual node
Virtual router and routes
Virtual service
Create and manage these in App Mesh
API, CLI, SDK, or
AWS Management Console
Proxies
Services
Service discovery
Configure and run proxies and services
on Amazon ECS, Fargate, Amazon EKS,
Amazon EC2
Service discovery with
AWS Cloud Map

Colorteller: app.colortellerdemo.com
Gateway
container
Gateway task
Colorteller
container
Colorteller task
http
Gateway
GET /color returns a color
Uses Colorteller to retrieve the color
Colorteller
Returns a pre-set color
Configured in service discovery as colorteller.local
http

Colorteller app “meshified”: app.colortellerdemo.com
Gateway
container
Gateway
http Colorteller
container
Colorteller
httphttp
Gateway
Proxy applies routing rules (e.g., path matching)
Proxy does the load balancingif there is more than one
Colorteller task running
Proxy does metrics, logging, and tracing
Colorteller
Proxy also does metrics, logging, and tracing
http

Partners

Roadmap
Today
Client-side load balancing
Path-based routing
Egress traffic
AWS Cloud Map service discovery
App Mesh console
AWS X-Ray tracing
Envoy supported tracing
CloudWatch Logs, metrics
StatsD, Prometheus metrics
Amazon ECS, Fargate integration
Amazon EKS integration
Amazon EC2 integration
Near term
AWS PrivateLink
AWS Cloud Map selectors
gRPC routing
Header-based routing
Cookie-based routing
Host-based routing
Timeout policy
Retry policy
Circuit breaker policy
End-to-end encryption
Longer term
mTLS
Mesh peering
Global rate limiting
Managed ingress
Other protocols

Getting started
Product overview
https://aws.amazon.com/app-mesh
Documentation
https://docs.aws.amazon.com/app-mesh/index.html
Examples
https://github.com/aws/aws-app-mesh-examples
Issues, roadmap, beta channel
https://github.com/aws/aws-app-mesh-roadmap

Thank you!
Nick Coult
Principal product manager
AWS

Introducing AWS App Mesh - MAD303 - Santa Clara AWS Summit

Recomendados

Recomendados

Mais conteúdo relacionado

Mais procurados

Mais procurados (20)

Semelhante a Introducing AWS App Mesh - MAD303 - Santa Clara AWS Summit

Semelhante a Introducing AWS App Mesh - MAD303 - Santa Clara AWS Summit (20)

Mais de Amazon Web Services

Mais de Amazon Web Services (20)

Introducing AWS App Mesh - MAD303 - Santa Clara AWS Summit