Cloud Native Architectures at AWS

Slide 1

Slide 1 text

Cloud Native Architectures at AWS Sezgin Küçükkaraaslan Co-founder & CTO @opsgenie @olric https://www.linkedin.com/in/sezgin-kucukkaraaslan/

Slide 2

Slide 2 text

● Why do we care? ● Try to find a definition ● Benefits ● Trade-offs ● AWS Tools Agenda

Slide 3

Slide 3 text

Software is eating the world (Marc Andreessen, 2011)

Slide 4

Slide 4 text

Apps demand speed, innovation, quality & amazing experience

Slide 5

Slide 5 text

Moving to Cloud ● Reduce Operation Costs. ● Move Faster ● Handle scale, resiliency and security better than doing it yourself (quality)

Slide 6

Slide 6 text

Reactive Manifesto https://www.reactivemanifesto.org/

Slide 7

Slide 7 text

What is Cloud Native ? ● Containerized ● Dynamically orchestrated ● Microservices oriented https://www.cncf.io/about/faq/

Slide 8

Slide 8 text

What is Cloud Native ? https://pivotal.io/cloud-native

Slide 9

Slide 9 text

Continuous Delivery Benefits ● Deliver software with fewer bugs and lower risk ● Release new features to market more frequently ● Respond to marketing conditions more quickly ● Life is saner for everyone

Slide 10

Slide 10 text

DevOps Benefits ● Faster resolution of problems ● More stable operating environments ● Higher customer satisfaction ● Improved communication and collaboration ● Improved code quality

Slide 11

Slide 11 text

Microservices Benefits ● Resilient / Flexible ● Independently scalable ● Freedom to choose technology ● Fast time to market - opens innovation opportunities ● Enables continuous delivery

Slide 12

Slide 12 text

Container Benefits ● Isolation ● Portability ● Rapid Deployment ● Lightweight footprint and minimal overhead

Slide 13

Slide 13 text

What else? ● Embraces disposable infrastructure/architecture ● Leverages value-added cloud services ● Scales globally

Slide 14

Slide 14 text

How should a cloud native application look like?

Slide 15

Slide 15 text

Distributed computing is hard ● Latency ● Timeouts ● Retries ● Backward / Forward compatibility ● Orchestration ● Understand CAP Theorem ● Transaction management The network is reliable Latency is zero Bandwidth is infinite The network is secure Topology doesn’t change There is one administrator Transport cost is zero The network is homogenous 8 Fallacies of Distributed Computing

Slide 16

Slide 16 text

Bulkheads

Slide 17

Slide 17 text

Circuit Breakers

Slide 18

Slide 18 text

No content

Slide 19

Slide 19 text

No content

Slide 20

Slide 20 text

No content

Slide 21

Slide 21 text

No content

Slide 22

Slide 22 text

Event Driven Architectures / Eventual Consistency

Slide 23

Slide 23 text

Event Sourcing & CQRS ● Distribution ● Availability ● Integration ● Analytics

Slide 24

Slide 24 text

Microservice Premium

Slide 25

Slide 25 text

Cloud Native at AWS

Slide 26

Slide 26 text

AWS Compute Offerings EC2 Virtual servers in the cloud ECS Container management EKS Managed Kubernetes Fargate Containers without servers Lambda Serverless compute

Slide 27

Slide 27 text

AWS Database Offerings Aurora Relational cloud database RDS Relational database DynamoDB Non-relational database ElastiCache In-memory datastore Redshift Data Warehousing Neptune Graph database

Slide 28

Slide 28 text

AWS Messaging Offerings SQS Simple messaging SNS Pub/Sub Kinesis Streaming MQ Managed ActiveMQ

Slide 29

Slide 29 text

AWS Management Offerings CloudWatch Observibility CloudFormation Infrastructure resource provisioning CloudTrail Auditing OpsWorks Configuration Management

Slide 30

Slide 30 text

AWS Development Offerings CodeCommit Source control (git) CodeBuild CI CodeDeploy Deploy code to compute services CodePipeline CI/CD

Slide 31

Slide 31 text

Thank you! Sezgin Küçükkaraaslan Co-founder & CTO @opsgenie @olric https://www.linkedin.com/in/sezgin-kucukkaraaslan/