Cloud Native Architecture Patterns Tutorial

CloudNativeArchitecturePatternsTutorial

2017O'ReillySoftwareArchitectureConference-NYCMattStine( )@mstine

http://www.mattstine.com

http://twitter.com/mstine

http://www.mattstine.com/

Introduction

YourInstructor

17yearsintheEnterpriseITindustry5yearsasaCloudPlatformandApplicationArchitectFrequentspeakerontheconferencecircuitHostoftheSoftwareArchitectureRadiopodcast

YourInstructor

http://www.oreilly.com/programming/free/migrating-cloud-native-application-architectures.csp

WorkshopComponentsLectureSocraticQ&ASessionsArchitectureKataSessions

AgendaClassIntroductionCloudNativeArchitectureFundamentals1:30-2:15PM

SocraticQ&ASession2:15-2:30PM

CloudNativeArchitecturePatterns2:30-3:30PM

SocraticQ&ASession3:30-3:45PM

AgendaCloudNativeArchitectureKatas-Setup3:45-4:00PM

CloudNativeArchitectureKatas-Create4:00-4:30PM

CloudNativeArchitectureKatas-Present4:30-5:00PM

TheBusinessDriversforArchitecturalChange

Agility

Disruption

Agility

-MarkAndressen

Softwareiseatingtheworld.

Agility

DisruptiveCharacteristicsSoftwareisprimaryengagementmodelNewandinnovativebusinessmodelsFastandfrequentdeliveriesHypothesis-drivendevelopment

Agility

TheWaterscrumfall

Agility

WaterscrumfallConsequences

SlowDeliveryLargeBatchSizesInfrequentFeedbackIncreasedWaste

Agility

DigitalTransformation

Resiliency

Disruptivecompaniesarealsoapproachingresiliency

differently.

Resiliency

Stoptryingtopreventmistakes.

Resiliency

Embracefailure.

Resiliency

FromMTBFtoMTTR

Resiliency

Weneedbettertoolsandtechniques.

Resiliency

Visibility

Resiliency

FaultIsolation

Resiliency

FaultTolerance

Resiliency

Scalability

Resiliency

AutomatedRecovery

AHigh-LevelOverviewofDevOpsandContinuous

Delivery

DevOps

THEGREATCONFLICT

DevOps

MyDefinition:DevOpsrepresentstheideaof

tearingdownorganizationalsilosandbuildingsharedtoolsets,

vocabularies,andcommunicationstructuresinserviceofaculture

focusedonasinglegoal:deliveringvaluerapidlyandsafely.

DevOps

THETHREEWAYS

DevOps

DevOps

TheFirstWay:Flow

DevOps

TheSecondWay:Feedback

DevOps

TheThirdWay:ContinualLearningand

Experimentation

ContinuousDelivery

MyDefinition:Technicallysupportingtheconcepttocashlifecyclebyprovingevery

sourcecodecommittobedeployabletoproductioninan

automatedfashion.

ContinuousDelivery

IngredientsConfigurationManagementContinuousIntegrationAutomatedTesting

ContinuousDelivery

CIDeveloperWorkflow

ContinuousDelivery

TheDeploymentPipeline

TheUniqueCharacteristicsofCloudInfrastructure

CloudInfrastructure

MyDefinition:Anycomputingenvironmentin

whichcomputing,networking,andstorageresourcescanbe

provisionedandreleasedelasticallyinanon-demand,self-service

manner.

CloudInfrastructure

DeploymentModelsPublicAmazonWebServicesGoogleCloudPlatformMicrosoftAzure

PrivateVMwarevSphereOpenStack

CommunityHybrid

CloudInfrastructure

ServiceModels

The*aaSPyramid

CloudInfrastructure

APIDrivenAutomationAuditAuthorizationAccounting

CloudInfrastructure

SpeedIfyouneedacomponent,createit!

LoadBalancersDatabases(SQL/NoSQL)MessageQueuesPrivateNetworksStorageVolumes

CloudInfrastructure

SpeedCaneliminate:

TicketSystemsApprovalProcessesWaitingQueuesConfigurationErrors

CloudInfrastructure

SpeedAsfastasyoucandesignthesystemarchitecturethatyouneed,youcanusuallyprovisionandbeginusingit.

CloudInfrastructure

ElasticGoodbyeCapacityPlanning!

CloudInfrastructure

ElasticCapacityPlanning

Peerintothecrystalball..."What'sthemostcapacitywe'llneed?"Guessincorrectly...BlowavailablecapacityonBlackFridayHundredsofidleCPUs

CloudInfrastructure

ElasticAsdemandincreases,wesimplyexpandcapacitybyprovisioningmoreresources

toservicethatdemand.

CloudInfrastructure

ElasticAsdemanddecreases,wesimplycontractcapacitybyreturningresourcestothe

pool.

CloudNativeArchitectureConcepts

ArchitectingforDevOps

Modularity


ThinkAbouttheThreeWays

Wewantaquantumofthisexperience.


DecompositionStrategiesWhat'syours?

BoundedContextsValueStreamsSingleResponsibilityPrincpleFailureDomainsAnti-CorruptionLayers


Strategiesarenotmutuallyexclusive!


SoWhatAboutModularity?LooseCouplingHighCohesionEncapsulationWell-DefinedInterface


GratuitousNodtoMicroservices!


Ifamicroserviceisn'tgivingyouThreeWaysValue,youprobablydon'tneedit.


Conway'sLawAnyorganizationthatdesignsasystem(definedbroadly)willproduceadesign

whosestructureisacopyoftheorganization'scommunicationstructure.


Ifyourarchitecturalandandorganizationaldecomposition

strategiesdon'talignwell,thenCONWAYWILLFIGHT

YOU!


Observability


ThinkAbouttheThreeWays

Weneedfeedbacktocreateasafersystemofworkandto(in)validateourhypotheses.


SeeFailureWhenItHappens


MeasureEverything


WhatisNormal?ValuesRatesofChangeMean?P95/99/99.9?


WhatisNormal?

http://bravenewgeek.com/everything-you-know-about-latency-is-wrong




ThisisanArchitecturalResponsibility

Architecturecanmakeobservabilityharder!OverheadConcernsToolsdon'tknowyourbusiness.

ArchitectingforContinuousDelivery

NOTE:ArchitectingforDevOpsaidsinContinuous

Delivery!


Addingsomelayers...


ThinkAboutFullLifecycleArchitecture


NealFord

Architectureisabstractuntilitisoperationalized.


Architecturesthataren'toperationalizedexistonlyon

whiteboards!


DeployabilityTestability

We'llexaminethesequalitiesbyaskingquestionsofourarchitectures.


Deployability


HaveyouautomatedALLofyourdeploymenttasks?


Canyoutransformabrandnewdeploymentenvironment

intoyourrunningarchitecturewithoutmanual

work?


Canyouvaryconfigurationacrossenvironmentswithout

rebuildingcode?


DoyoudeploylikethisEVERYWHERE?


Canyoudothiswithoutyourusersnoticing?


Testability


HaveyouautomatedALLtestingtasksthatyou

possiblycan?


Doyouhavetodeployallthethingstotestanything?


Iftestingisanexperiment,canyoucontroleverythingexceptyourexperimental

variable?


Canyourunthesametestsagainstanyenvironment(includingproduction)?


Canyouverifythatyoucontinuetomeetyour

contractualobligations?

ArchitectingforCloudInfrastructure

CloudCapabilitiesAPI-drivenSpeedElasticityGeographySpecializedServices


ExploitingthecapabilitiesofCloudcanenhanceourability

topracticeDevOpsandContinuousDelivery!


DisposabilityReplaceability

We'llexaminethesequalitiesbyaskingquestionsofourarchitectures.


Disposableadjective

1. designedfororcapableofbeingthrownawayafterbeingusedorusedup:disposableplasticspoons;adisposablecigarettelighter.

2. freeforuse;available:Everydisposablevehiclewassent.

http://www.dictionary.com/browse/disposable


Replaceverb

1. toassumetheformerrole,position,orfunctionof;substitutefor(apersonorthing):Electricityhasreplacedgasinlighting.

2. toprovideasubstituteorequivalentintheplaceof:toreplaceabrokendish.

http://www.dictionary.com/browse/replace


Consequencenoun

1. anactorinstanceoffollowingsomethingasaneffect,result,oroutcome.

2. importanceorsignificance:amatterofnoconsequence.

http://www.dictionary.com/browse/consequence


Disposability

CanIdestroyaserviceinstanceatanytimewithout

consequence?


Disposability

CanIrepavetheentirearchitectureatanytimewithoutconsequence?


Disposability

CanIrespondtochangesindemandbyaddingorremovinginstancesofa

servicewithoutconsequence?


Replaceability

CanIreplaceasickserviceinstancewithabrandnew

copywithoutconsequence?


Replaceability

CanIroutetraffictoanyavailableserviceinstance

withoutconsequence?


Replaceability

IfIloseanAZorRegion,canIroutetraffictoanotherwithoutconsequence?


Replaceability

CanIswapbetweenmultipleimplementationsofthesame

servicecontractwithoutconsequence?


Replaceability

CanIswapbetweenmultiplerunningversionsofaservice

withoutconsequence?


TheseareArchitecturalResponsibilities

Architecturecanmakedisposabilityimpossible.Architecturecanmakereplaceabilityimpossible.Architecturemusttakechargeofremovingtheconsequencesofdisposingandreplacingserviceinstances.

Summary

ArchitecturalDecisionMakingCan:

EnhanceorDetractfromOurAbilitytoPracticeDevOpsEnhanceorDetractfromOurAbilitytoPracticeContinuousDeliveryExploitorWastetheCharacteristicsofCloudInfrastructure

Summary

Wecouldhavecalledthis"DevOpsNative"or

"ContinuousDeliveryNative"Architecture!

Summary

DevOpsNativeArchitecture

Summary

Balancing:

AgilityandResilience

Summary

SupportedBy:

DevOpsandContinuousDelivery

Summary

OnaFoundationof:

CloudandArchitecture

SocraticQ&A

CloudNativeArchitecturePatterns

Overview

Pattern-OrientedSoftwareArchitecture,Volume1:ASystemofPatterns

Patternsshould...bedescribeduniformly.Thishelpsustocompareonepattern

withanother...

Overview

DesignPatterns:ElementsofReusableObject-OrientedSoftware

Wedescribedesignpatternsusingaconsistentformat...makingdesign

patternseasiertolearn,compare,anduse.

Overview

BrickandMortarPatternTemplateContextThebasicsituationinwhichwefindourselvesworking.

ProblemPresentstheproblemasasystemforceswhichmustbebalanced.

SolutionDescribesthecomponentsthatmakeupthegeneralsolution,howtheyrelatetooneanother,andtheirruntimeinteractions.

Overview

BrickandMortarLanguageStructureBrickPatternsPatternsforconstructingindividual(micro)services.

MortarPatternsPatternsforcomposingbricksintocompletedistributedsystems.

Overview

BrickPatternsExternalizationPatternsStructuralpatternsforcreatingdeployable,disposable,andreplaceablebricks.

ExternalizedConfigurationExternalizedStateExternalizedChannels

RuntimePatternsBehavioralpatternsforcreatingdeployable,replaceable,andobservablebricks.

RuntimeReconfigurationConcurrentExecutionBrickTelemetry

Overview

MortarPatternsDistributedSystemsPatternsCompositionpatternsaddressingcommondistributedsystemschallenges.

ServiceDiscoveryEdgeGatewayFaultTolerance

IntegrationPatternsCompositionpatternsaddressingintegrationandobservabilitychallenges.

Event-DrivenSystemContractManagementIntegrationTelemetry

Overview

BrickandMortarLanguageRelationships

BrickPatternsExternalizedConfigurationExternalizedStateBrickTelemetry

ExternalizedConfiguration

ContextandProblem

ContextAnapplication'sconfigurationwillvaryindependentlyfromitscodethroughout

itslifecycle.

ContextandProblem

ProblemTraditionaltechniquesformanagingconfigurationtightlycouplethesetwo

orthogonalconcepts.

ContextandProblem

ForcesDifferentenvironmentswillhavedifferentconfigurationsettings:resourcehandlestothedatabase(e.g.aJDBCURL)credentialstoexternalservices(e.g.AmazonS3)per-deployvaluessuchasthecanonicalhostname(e.g.blog-test.example.comvs.blog-prod.example.com)featuresthataretoggledonoroff

ContextandProblem

ForcesConfigurationisoftenbundledwithindeploymentartifacts(e.g.Javapropertiesfiles).Buildprocessesoftenmodifyconfigurationbasedonarguments.TheDeploymentPipelineshouldonlybuildeachdeploymentartifactonce,anddeploythesameartifacttomultipleenvironments.

LIVEARCHITECTURE!

ExternalizedState

ContextandProblem

ContextDisposabilityandReplaceabilityrequire

theeliminationof"snowflakedeployments"fromthearchitecture.

ContextandProblem

ProblemTraditionalstatemanagement

techniquespreventusfromachieving"phoenixdeployments."

ContextandProblem

ForcesEarlywebarchitecturesemphasizedserver-sidestatemanagement:FatClientstoThinClientsVerticallyScaledCacheManagementStatefulScaffoldingonStatelessProtocol(HTTP)

ContextandProblem

ForcesCloudInfrastructure:ResourceLimitedHorizontalScaleLimitedLoadBalancerSupportforSessionsLimited(No)SupportforPersistentLocalDisk

LIVEARCHITECTURE!

BrickTelemetry

ContextandProblem

ContextRealizingtheDevOpsWayofFeedbackrequiresthatwehavevisibilityintoboth

thebusinessvalueandtechnicalbehaviorgeneratedbyourservices.

ContextandProblem

ProblemCommonapproachestoservicevisibilityfallshortofthearchitecturalqualities

thatweneed.

ContextandProblem

ForcesVisibilityisoftenaccomplishedviapostfactoapplicationofagent-basedmonitoringtools.Agent-basedmonitoringtoolsdon'tunderstandbusinessvalue.Determininganapplication'shealthoftenrequirescomplexlogic.Traceabilityofanapplicationisdifficult(orimpossible)toaccomplishwithOTSsolutions.

LIVEARCHITECTURE!

MortarPatternsServiceDiscoveryEdgeGatewayFaultTolerance

ServiceDiscovery

ContextandProblem

ContextDecompositionofarchitectureintoservicesleadstoincreasinglymore

distributedsystems.

ContextandProblem

ProblemAssystemsbecomedistributed,andasserviceinstancelifecyclesbecomemoredynamicandindependent,locationofandcommunicationwithdependencies

becomesmorechallenging.

ContextandProblem

ForcesCloudplatformsoftenassignauto-generated,internalhostnamesorprivateIP'stoserviceinstances.Asservicesarescaledandunhealthyinstancesarereplaced,theaddressesofaservice'sinstancesareconstantlychanging.Bindingaservicetoanythingotherthanlogicalnamesforitsdependenciesleadstofrictioninthearchitecturallifecycle.

ContextandProblem

ForcesApplyingConcurrentExecutionismademoredifficult(orimpossible)whenbindingservicestofixedaddressesfortheirdependencies.Wemaywanttoremoveaserviceinstancefromtheavailablepoolbutkeepitrunningtotroubleshootaproblem.

LIVEARCHITECTURE!

EdgeGateway

ContextandProblem

ContextDecomposedarchitecturesmustalwaysberecomposed.Thisrecompositionoftenhappenswithintheuserinterfacelayerof

anapplication.

ContextandProblem

ProblemRecomposinganarchitecturewithintheUserInterfacelayerpresentssignificantcomplexitiesthatcanleadtodecreasedagilityanddegradeduserexperience.

ContextandProblem

ForcesSystemsoftenmustsupportmultipleuserexperienceoptions(web/mobile/AVR).RecomposingarchitecturesastheUIlayercanrequireexposingthearchitecturetothepublicnetwork.APIneedsforamobiledeviceareoftenquitedifferentfromawebUI.

ContextandProblem

ForcesExposinganetworkgraphtomobiledevicescanincreaselatency,increasedatausage,anddegradebatterylife.UIplatformsmaynotsupporttheintegrationarchitectureusedforallservices.Nativeappsoftenhavelongerupgradecycles.Recomposingthearchitecturetherecanleadtofrictioninthearchitecturallifecycle.

LIVEARCHITECTURE!

FaultTolerance

ContextandProblem

ContextInordertoaccomplishitsassignedtasks,eachbrickwillneedtocommunicatewithotherbricks,andwithexternalsystems,

towhichwe'llcollectivelyreferasdependencies.

ContextandProblem

ProblemWhenabrick'sdependenciesbecomeunhealthy,unreachable,orslowerthannormaltorespond,thatbrick'sownperformanceisdegraded,andsuchdegredationcanpotentiallycascade

acrosstheentirearchitecture.

ContextandProblem

ForcesThenetworkisnotreliable.Latencyisnon-zeroandunpredictable.Serviceavailabilityisaproductofitsdependencies'availabilities.

ContextandProblem

ForcesFailurescanbetransient.Failurescancascade.Anincorrectorstaleresponseisoftenpreferabletonoresponse.

LIVEARCHITECTURE!

SocraticQ&A

CloudNativeArchitectureKatas

Setup

WhatareArchitectureKatas?Takemetotherules!

https://archkatas.herokuapp.com/rules.html

ToCloudNativeAddthefollowingtoyourrequirements:

Day1asacompanywe'reagreeingtoguideourselvesbyDevOpsprinciplesandpracticeContinuousDelivery.Wehavenoinfrastructure;we'lluseoneormorepubliccloudproviderstodeliveroursoftware.Thinkdeeplyaboutyourdecompositionstrategyandwhatadvantagesitwillbringyou.UsetheCNAPatternsyouknowsofarinordertoenableyourarchitecturestotheseends.

KataChoiceshttp://bit.ly/cna-kata-choices

http://bit.ly/cna-kata-choices