Migrate-Critical-Workload-to-AWS-From-Domain-Driven-Design-perspective

2. © 2019, Amazon Web Services, Inc. or its Affiliates. All rights reserved. Migrate Critical Workload to AWS From Domain Driven Design perspective Kim Kao, Solutions Architect yikaikao@amazon.com @Yikaikao Domain Driven Design(DDD Taiwan) Kim Kao

3. Things change.

4. © 2019, Amazon Web Services, Inc. or its Affiliates. All rights reserved. Enterprise face a challenging environment ? High customer expectations, fickleness Low barriers to entry Constant, rapid change and uncertainty

6. © 2019, Amazon Web Services, Inc. or its Affiliates. All rights reserved. 1. Rapid series innovation 2. Product teams 3. Relentless training 4. Application modernization 5. Embedded security 6. IT as a partner of the business 1. The big bang 2. Project approach - siloed 3. Don’t have time for training 4. Non-agile approach 5. Bolt on security 6. IT as a contracted service Enterprise challenges Enterprise opportunity

8. © 2019, Amazon Web Services, Inc. or its Affiliates. All rights reserved. • Endless agile MVP market experiments • Platforms that rapidly scale best results • Compete again and again to win and retain customers • Start with small teams, small slices of value, and small investments “Nail it before you scale it” Rapid series innovation

9. © 2019, Amazon Web Services, Inc. or its Affiliates. All rights reserved. The Monolith “…a single-tiered software application in which the user interface and data access code are combined into a single program from a single platform. A monolithic application is self-contained, and independent from other computing applications.” - Wikipedia

10. © 2019, Amazon Web Services, Inc. or its Affiliates. All rights reserved. Monolith == Traditional Application • Pros: • At first… • Simple • No over-engineering • In-process latencies • Single code base • Resource efficient at small scale • Cons: • Modularity is hard to enforce as app grows • Can only scale up! • All or nothing deployment • Long release cycles • Slow to react to customer demand

13. © 2019, Amazon Web Services, Inc. or its Affiliates. All rights reserved. Methodical migration process Visualize the cloud adoption effort from planning to operating on AWS Evaluate Plan Design Migrate Optimize • Discovery • Migration patterns • Well Architected • Tool selection • Test planning • Cutover planning • Migration workloads • Migration tools • Validation & cutover • Operation • Optimization • Migration Readiness Assessment • On-boarding • Planning and SOW • Portfolio discovery • Requirements collection • Landing Zone • People - skills and organization • Business case, TCO

14. © 2019, Amazon Web Services, Inc. or its Affiliates. All rights reserved. Portfolio discovery Goals: • Determine resource allocation in the AWS environment • Develop a prioritized backlog of applications to feed migration • Assess project migration costs and run costs Evaluate Discover & Plan Design Migrate Optimize

15. © 2019, Amazon Web Services, Inc. or its Affiliates. All rights reserved. Questions & challenges on the Journey • Where to start? • What to break out? • Dependencies? • Works as expected? • Users happy? • Does it scale? • Does it perform? • How to automate? • Works as expected? • Users happy? • How to optimize? Does it perform? • How to automate? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? From On-Premises Monolith Via Containerized Services To Functions & Cloud Services

18. © 2019, Amazon Web Services, Inc. or its Affiliates. All rights reserved. Rapid innovation is an imperative Exploit existing capabilities Make your numbers Explore new opportunities Incubate new ideas

22. © 2018, Amazon Web Services, Inc. or its affiliates. All rights reserved. “Any organization that designs a system… will inevitably produce a design whose structure is a copy of the organization’s communication structure.” — Melvin Conway a.k.a  Silo

25. © 2019, Amazon Web Services, Inc. or its Affiliates. All rights reserved. An Engineer promised his boss to develop an app. Now what? Step 0: Requirement analysis, high level design… Step 1: Design decisions - what to use? Serverless web app with …an API ??? …access to existing data stored in ??? …static content served by ??? …dynamic content/business logic encoded as ??? What we need

30. © 2019, Amazon Web Services, Inc. or its Affiliates. All rights reserved. Divide Complexity problem by Event Storming “ All the key Stakeholders in the same room with an unlimited modelling space Using stickies as Domain Events ” ~ Alberto Brandolini

35. © 2019, Amazon Web Services, Inc. or its Affiliates. All rights reserved. Way to collaborate • Point out the events • Who send the command • Find the Noun(s) • Have all team voices Commands Events Aggregate

37. © 2019, Amazon Web Services, Inc. or its Affiliates. All rights reserved. Approach • Collect the “Aggregates” which stand for similar concept in the “Bounded Context”, draw a circle shape. • Prioritize the “Domains”, which one is Core Domain, rest for Sub Domain, even Utility Domain. • Get Consensus, not Compromise • Focus on Core Domain

41. © 2019, Amazon Web Services, Inc. or its Affiliates. All rights reserved. New Business operation attempt Keep travelers safety in Clean environment for Variety Pillow Refund when Not Satisfied Easy to fall asleep Stay like home During the stay

42. © 2019, Amazon Web Services, Inc. or its Affiliates. All rights reserved. Free WIFI Power Station Agile Solution Architecture Industrialized Patterns & Solutions Comfortable Pillow Choices Customized Service Cross hotel Vending Machine Self Checkout POS Digital Door-lock 360º Customer Persona IT operation response in time New Technology required Business Driven Evolution Super Hotel Operation

45. © 2019, Amazon Web Services, Inc. or its Affiliates. All rights reserved. Scenario : Guest Check in & out flow Confirmed Booking Presented E-Keys Verified Booking guest Took elevator Filled up Guest Info Opened Room Door Delivered Stay policies Acted In Room

52. © 2019, Amazon Web Services, Inc. or its Affiliates. All rights reserved. Relational Referential integrity, ACID transactions, schema- on-write Lift and shift, ERP, CRM, finance Key-value High throughput, low- latency reads and writes, endless scale Real-time bidding, shopping cart, social, product catalog, customer preferences Document Store documents and quickly access querying on any attribute Content management, personalization, mobile In-memory Query by key with microsecond latency Leaderboards, real-time analytics, caching Graph Quickly and easily create and navigate relationships between data Fraud detection, social networking, recommendation engine Time-series Collect, store, and process data sequenced by time IoT applications, event tracking Ledger Complete, immutable, and verifiable history of all changes to application data Systems of record, supply chain, health care, registrations, financial Amazon QLDB Amazon Aurora Amazon RDS Amazon DynamoDB Amazon DocumentDB Amazon ElastiCache Amazon Neptune Amazon Timestream Booking Guest 360 E-Door LockPromotion Advertise Digital Assets PaymentPillow Staff

54. © 2019, Amazon Web Services, Inc. or its Affiliates. All rights reserved. • Circle Study group • Implementing Domain Driven Design • Volunteer reader lead • Hands-on workshop • Try Pair programming

Migrate-Critical-Workload-to-AWS-From-Domain-Driven-Design-perspective

Du liest eine Vorschau.

Hier ansehen

Migrate-Critical-Workload-to-AWS-From-Domain-Driven-Design-perspective

Weitere Verwandte Inhalte

Diashows für Sie (20)

Ähnlich wie Migrate-Critical-Workload-to-AWS-From-Domain-Driven-Design-perspective (20)

Weitere von Amazon Web Services (20)