© 2016, Amazon Web Services, Inc. or its Affiliates. All rights reserved.

Cloud First: New Architectures for New Infrastructure

Ian Massingham @IanMmmm Chief Evangelist (EMEA) Amazon Web Services

Implementing new architectures in the AWS Cloud

The AWS Well Architected Framework

Topics for this session

Monoliths to Microservices: Challenges with Monolithic Software Architecture

Harder to maintain and evolve

Scalability is compromised

Lack of agility

Reduced development pace

Operational complexity

Longer build/test/release cycles

Lack of innovation

Customers frustration

Anatomy of a Microservice

Software modules (application, libraries, and so on)

Data store (for example, Amazon DynamoDB, Amazon RDS, Amazon ElastiCache, Amazon S3)

Public APIaddProductDetails(ProductId id, ProductDetails details) removeProductDetails(ProductId id) getProductDetails(ProductId id) : ProductDetails

Microservice

Microservice = service-oriented architecture + “small” public API

Can be built by small development teams

Microservice

2-pizza team (typically 4-8 people)

Warehouse employee using microservice through web/mobile interface

“Pick customer orders” team

Rely only on each other’s public API

public API public API

Microservice Microservice

Creating a web of microservices

Pick customer orders

Report defects

Track shipments

Product details

Store products in the warehouse

Monoliths to Microservices: Organisational Considerations

“Any organization that designs a system (defined broadly) will produce a design whose structure is a copy of the organization's communication structure.”

Melvyn Conway, 1967

Conway’s Law

AWS Services for implementing Microservices

Elastic Load Balancing

EC2 Container Service

EC2

AWS Lambda

API Gateway

Identity & Access Management Key Management Service

DynamoDB

Relational Database Service

N-TIER MODEL

SERVERLESS MODEL

MOBILE CHAT APP

AD DATA ANALYTICS AND ROUTING

MOBILE APP ANALYTICS

IMAGE CONTENT FILTERING

REAL-TIME VIDEO AD BIDDING

NEWS CONTENT PROCESSING

GENE SEQUENCE SEARCH

CLOUD TELEPHONY

DATA PROCESSING

WEB APPLICATIONS

WEB APPLICATIONSTHREAT INTELLIGENCE AND ANALYTICS

NEWS CONTENT PROCESSING

GAME METRICS ANALYTICS

Serverless Applications in Production on AWS

The AWS Well-Architected Framework

Strategies & best practices for architecting in the cloud

Questions that allow you to measure your architecture against best practices

Making informed decisions about architecture in the cloud, understanding the potential impact of decisions

Questions are the starting point, you should think actively about “what if” and failure scenarios

Well-Architected Design Principles

Stop guessing your capacity needs

Test systems at production scale

Lower the risk of architecture change

Automate to make architectural experimentation easier

Allow for evolutionary architectures

Security Reliability Performance Efficiency

Cost Optimisation

Pillars of Well-Architected

Pillars of Well-Architected

For you to use to evaluate how well an architecture is aligned to AWS best practices.

Questions

Common Uses of Well-Architected

Learn how to build cloud native architectures

Build a backlog

Use as a gating mechanism before launch

Compare maturity of different teams

Due-diligence for acquisitions

© 2016, Amazon Web Services, Inc. or its Affiliates. All rights reserved.

Want to know more? Visit the Ask an Architect Booth

Ian Massingham @IanMmmm Chief Evangelist (EMEA) Amazon Web Services