Microserviceson AWS: Architectural Patterns and Best Practices... · • Data source integrations...

© 2019, Amazon Web Services, Inc. or its affiliates. All rights reserved.S U M M I T

Microservices on AWS: Architectural Patterns and Best PracticesSascha MölleringSenior Solutions ArchitectAmazon Web Service EMEA SARL

S e s s i o n I D


Agenda

Options for architecting your microservices

Serverless best practices

Containers best practices

Serverless and containers combined


Related breakouts

Observability for Modern ApplicationsChristoph Kassen

Extending EKS with open source toolsRic Harvey

Best Practices for Safe Deployments on AWS Lambda and Amazon API Gateway

Danilo Poccia

S U M M I T © 2019, Amazon Web Services, Inc. or its affiliates. All rights reserved.


When the impact of change is small,release velocity can increase

MonolithDoes everything

MicroservicesDoes one thing


MICROSERVICE API

API MICROSERVICE

MICROSERVICEEVEN

T

APIMICROSERVICE

EVENT

API MICROSERVICE

APPLICATION

Mobile client

Client

IoT

PERSISTENCE PERSISTENCE


Options for architecting your microservices

AWS Lambda

Amazon EKS

Amazon ECS

AWS Fargate

Containers Serverless


Containers: ECS, EKS, Fargate• Portability• Control• Rich ecosystem


Serverless: Lambda• Event-driven framework• Multiple invocation models• Opinionated


What is serverless?

No infrastructure provisioning, no management

Automatic scaling

Pay for value Highly available and secure


Comparison of operational responsibility

AWS LambdaServerless functions

AWS FargateServerless containers

ECS/EKSContainer-management as a service

EC2Infrastructure-as-a-Service

More opinionated

Less opinionated

AWS manages Customer manages

• Data source integrations• Physical hardware, software, networking,

and facilities• Provisioning

• Application code

• Container orchestration, provisioning• Cluster scaling• Physical hardware, host OS/kernel,

networking, and facilities

• Application code• Data source integrations• Security config and updates, network config,

management tasks

• Container orchestration control plane• Physical hardware software,

networking, and facilities

• Application code• Data source integrations• Work clusters• Security config and updates, network config,

firewall, management tasks

• Physical hardware software, networking, and facilities

• Application code• Data source integrations• Scaling• Security config and updates, network config,

management tasks• Provisioning, managing scaling and

patching of servers



What if I can’t decide?

Lambda Function


Inter-container communication*

or storage-intensive?

Desire orchestration portability OR open

source fan? Amazon EKS

Are you comfortable managing your own

infrastructure?Amazon ECSAWS Fargate

Deployment Package size

<= 50MB

Desired Service runtime <= 15

minutes?

AWS Lambda

Decision Tree – well, almost!


Most important!

• Ask yourself: do you really need containers?• Start with a serverless approach!• Switch to containers if necessary!



Lambda considerations and best practices

AWS Lambda is stateless—architect accordingly• Assume no affinity with underlying compute infrastructure• Local filesystem access and child process may not extend beyond

the lifetime of the Lambda request


Lambda considerations and best practices

Can your Lambda functions survive the cold?

• AWS clients and database clients outside the scope of the handler

• CloudWatch Events for warmth• VPC support: ENI attached (cold start)

import sys import logging import rds_configimport pymysql

rds_host = "rds-instance" db_name = rds_config.db_nametry:

conn = pymysql.connect( except:

logger.error("ERROR:def handler(event, context):

with conn.cursor() as cur:

Executes with each invocation

Executes during cold start


Lambda Best Practices

• Minimize package size • Separate the Lambda handler from core logic• Use Environment Variables to modify operational behavior• Self-contain dependencies• Leverage “Max Memory Used” to right-size your functions



Stream processing characteristics

• High ingest rate• Near real-time processing• Spiky traffic• Message durability and ordering


Streaming data ingestion

Delivery metrics

Buffered files

Table loads

Domain loads

Source record backup

Transformations &enrichment Lookup tables

Raw records

Lookup

Transformed records

Transformed records

Raw records

Delivery stream

ProducersGroup

KinesisAgent


Best practices

• Tune Firehose buffer size and buffer interval

• Enable compression

• Enable Source Record Backup

• Amazon Redshift Best Practices for Loading Data

http://docs.aws.amazon.com/redshift/latest/dg/c_loading-data-best-practices.html


Amazon Kinesis Data Streams and AWS Lambda

• Number of Amazon Kinesis Streams shards corresponds to concurrent invocations of Lambda function

• Batch size = max number of records per Lambda function invocation

Data Stream Processor function

Streaming source Other AWS services


Fan-out pattern

Strict message ordering vs higher throughput & lower latency

Data Stream Dispatcher function Processor function

Increase throughput, reduce processing latency

Streaming source



Think about your applications‘ needs


Optimizing your container

• Optimize for smaller size

• Use a minimalist operating system

• Not all runtimes are equal!


Popular base images have a huge range by size

REPOSITORY SIZEnode:latest 674MBjava:latest 643MBnode:slim 184MBubuntu:latest 85.8MBalpine:latest 4.41MBbusybox:latest 1.15MB



Multi-stage Docker build



1

2



1

2

3

4


Optimize pods

• How many sidecar containers?

• Admission controllers add overhead!

• Keep pods lightweight!


Optimize pod placement

Make sure you use resource constraints:

• Request the baseline average resource needs of the app

• Put a limit on the max resources of a pod



New: Lambda Layers

• Share code between functions (crosscutting concerns)

• Promote separation of responsibilities

• Built in support for secure sharing by ecosystem


New: Custom Runtimes

Bring any Linux compatible language runtime

Powered by new Runtime API

Custom runtimes distributed as “layers”


AWS Lambda Container Image Convertercd example

docker build -t lambda-php .

./bin/local/img2lambda -i lambda-php:latest -r us-east-1

https://github.com/awslabs/aws-lambda-container-image-converter

https://github.com/awslabs/aws-lambda-container-image-converter


MICROSERVICE API

API MICROSERVICE

MICROSERVICE

EVENT

APIMICROSERVICE

EVENT

API MICROSERVICE

APPLICATION

Mobile client

Client

IoT

PERSISTENCE PERSISTENCE

Go build something!


Thank you!


Sascha Mö[email protected]: @sascha242

mailto:[email protected]

© 2019, Amazon Web Services, Inc. or its affiliates. All rights reserved.S U M M I TS U M M I T © 2019, Amazon Web Services, Inc. or its affiliates. All rights reserved.

Date post:	25-Mar-2020
Category:	Documents
Upload:	others
View:	16 times
Download:	0 times

Microserviceson AWS: Architectural Patterns and Best Practices... · • Data source integrations...

Documents