FUNDAMENTALS SCALABILITY

Transcription

1 FUNDAMENTALS OF SCALABILITY

2 Dimitri Holsteens Software architect Stijn Van Eynde Software

3 INTRODUCTION AZURE SCALABILITY BUILDING BLOCKS CQRS

4 The search for the holy blueprint

5 Recipes and ingredients

6

7

8

9 A balancing act

10 UP NEXT Azure Scalability Building Blocks Technical partitioning with CQRS pattern break Functional partitioning with Microservices Polyglot Persistence Componentization through libraries

11 AZURE SCALABILITY BUILDING BLOCKS AZURE SQL AUTO SCALING LOAD BALANCING

12 AZURE

13 AZURE

14 AZURE

15 AZURE SQL

16 SQL Server SQL Server VM SQL Database PaaS IaaS Physical HARDWARE & SOFTWARE COSTS, ADMIN COSTS, FULL CONTROL THE RELATIONAL DATABASE CONTINUUM PAY-AS-YOU-GO, ELASTIC SCALE, ZERO ADMIN

17 AZURE SQL FEATURES

18 AZURE SQL - HIGH AVAILABILITY 18

19 Tiers Basic => 5 /mo Standard => /mo Premium => 393-5,904 /mo AZURE SQL PERFORMANCE & SCALABILITY

20 Tiers Basic => 7 days Standard => 14 days Premium => 35 days AZURE SQL - POINT-IN-TIME RESTORE

21 AZURE SQL ELASTIC DATABASE POOLS

22 AZURE SQL SHARDING

23 AUTOSCALING

24 HOW CAN SCALING BE DONE?

25 HOW CAN SCALING BE DONE?

26 SCALING CLOUD SERVICES

27 SCALING - PORTAL

28 LOAD BALANCING

29 AZURE LOAD BALANCER Portforwarding Automatic reconfiguration on scale out/down Service monitoring

30 Improve availability Improve responsiveness Automatic reconfiguration on scale out/down Traffic distribution for large, complex deployments AZURE TRAFFIC MANAGER

31 AZURE CDN Lower latencies Improved availability and performance for your apps and services Dynamic content

32 UPCOMING Application Insights Operational Insights

33 Technical partitioning with CQRS pattern UP NEXT break Functional partitioning with Microservices Polyglot Persistence Componentization through libraries

34

35

36 But first... How many of you......have heard of CQRS?...know what the acronym stands for?...have seen it implemented in some form or another into an application?...have implemented in some form or another into an application?

37 A single model cannot appropriate for reporting, searching and transactional behavior. Greg Young

38 Command Query Responsibility Segregation

39 STEREOTYPICAL ARCHITECTURE

40 Scale up Scale out HOW DO YOU SCALE A MONOLITHIC ARCHITECTURE?

41 Same entityset Write & read on same repository Very CRUD based approach Imbalance in amount of write & read operations Datastructure optimized for writes Difficult to employ security ONE MODEL TO RULE THEM ALL

42 Phase 1 Segregate write from read operations Phase 2 Different models Phase 3 Different data stores CQRS TO THE RESCUE

43 Maximize scalability Enhance performance Better manage security Flexibility that will support the growth of your application over time BENEFITS

44 Move away from the monolith How to enable scalability for your existing monolithic architecture by gradually applying CQRS principles

45 IN THE BEGINNING

46 Data tier Service tier Datapersistance Client applications Web application X Console application Y Datastore Business Logic Windows Service A... WCF Service Layer AFTER A WHILE

47 Data tier DB API Reporting Client applications Web application X Console application Y Legacy Service tier Windows Service A Datastore DP BL WCF... THE DATABASE API REPORTING DATABASE

48 Data tier DB API Reporting Client applications Web application X Console application Y Legacy Service tier Windows Service A Datastore DP BL WCF... THE THIN READ LAYER

49 Data tier DB API Reporting Command Datastore Legacy Service tier DP BL WCF Client applications Web application X Console application Y Windows Service A... THE DATABASE API COMMAND DATABASE

50 Data tier Client applications DB API Web application X Reporting Command DP New Service tier BL API Console application Y Windows Service A Datastore Legacy Service tier... DP BL WCF REROUTE AND/OR MIGRATE

51 Data tier DB API Reporting Client applications Web application X Console application Y ServiceBus Windows Service A Datastore Command DP Service tier BL API... SERVICEBUS

52 Consistency Enable your data to be consistent all the time Availability Enable your data to be accessible all the time Partition Tolerance Enable your data to scale infinitly Result: stale data EVENTUAL CONSISTENCY

53 Once requested data leaves the database server, it might by out-of-date. ALWAYS WORKING WITH STALE DATA

54 Data tier Client applications DB API Web application X Reporting ServiceBus Cache-Aside Console application Y Windows Service A Datastore Command DP Service tier BL API... CACHE-ASIDE

55 Physically dividing the data in separate stores for read and write operations will increase performance and maximize security of a system, but it will also add considerable complexity to your application. Consider on which sections of your application CQRS can be a benefit and start by applying it there. Learn from the experience. Don t use it in simple or small business applications where a simple CRUD approach is more feasible. IMPLEMENT WITH CARE! ISSUES AND CONSIDERATIONS

56 QUESTIONS?