技术白皮书：AWS 云采用框架 – 平台视角

1/1技术白皮书：AWS云采用框架–平台视角AWSCloudAdoptionFramework

PlatformPerspective

November2015

?2015,AmazonWebServices,Inc.oritsaffiliates.Allrightsreserved.

Notices

Thisdocumentisprovidedforinformationalpurposesonly.ItrepresentsAWS’s

currentproductofferingsandpracticesasofthedateofissueofthisdocument,

whicharesubjecttochangewithoutnotice.Customersareresponsiblefor

makingtheirownindependentassessmentoftheinformationinthisdocument

andanyuseofAWS’sproductsorservices,eachofwhichisprovided“asis”

withoutwarrantyofanykind,whetherexpressorimplied.Thisdocumentdoes

notcreateanywarranties,representations,contractualcommitments,conditions

orassurancesfromAWS,itsaffiliates,suppliersorlicensors.Theresponsibilities

andliabilitiesofAWStoitscustomersarecontrolledbyAWSagreements,and

thisdocumentisnotpartof,nordoesitmodify,anyagreementbetweenAWS

anditscustomers.

Page2of19

Contents

Abstract4

Introduction4

DesignArchitecture7

ConceptualArchitectureActivity7

LogicalArchitectureActivity8

Considerations10

ImplementationArchitecture11

Considerations13

ArchitectureOptimization14

CloudDesignPrinciplesandPatternsActivity14

ApplicationMigrationPatternsActivity15

Considerations17

CAFTaxonomyandTerms18

Conclusion19

Notes19Page3of19

Abstract

TheAmazonWebServices(AWS)CloudAdoptionFramework(CAF)1providesbestpracticesandprescriptiveguidancetoaccelerateanorganization'smovetocloudcomputing.TheCAFguidanceisbrokenintoanumberofareasoffocusthatarerelevanttoimplementingcloud-basedITsystems.Thesefocusareasarecalledperspectives.Eachperspectiveiscoveredinaseparatewhitepaper.ThiswhitepapercoversthePlatformPerspective,whichfocusesondesigning,implementing,andoptimizingthearchitectureoftheAWStechnologythatyouuseinyourcloudadoptioninitiative.

Introduction

YourorganizationcanusetheAWS

CloudAdoptionFramework(CAF)

guidancetoexplorehowdifferent

departmentscanworktogetheron

oneormorecloudadoptioninitiative.

Guidanceisseparatedintothe

followingfocusareas,called

perspectives:BusinessPerspective,

PlatformPerspective,Maturity

Perspective,PeoplePerspective,

ProcessPerspective,Operations

Perspective,andSecurityPerspective.

ThePlatformPerspectivecomponents

describethestructureanddesignofa

cloud-basedITsystem,orahybridIT

systemthatspansbothcloudand

non-cloudenvironments.

Therestofthiswhitepaperdescribes

howtheperspectivestranslateintoactivitiesthatyourorganizationcanperform.Thiswhitepapercoversdesignarchitectureandimplementationarchitecture.Youcanalsobenefitfromprinciplesandpatternsforrapidlyimplementingor

Figure1ComponentsofthePlatform

Perspective

experimentingwithnewsolutionsonthecloud,ormigratingexistingnon-cloudsolutionstothecloud,whichwillbecoveredaspartofoptimization.

EmbracingAgility

Manyorganizationsalreadyuseagiledevelopmenttoincreasethevelocityoftheiranticipatedbusinessoutcomes.However,somebusinessesexperiencedifficultyinachievingagilityallthewaythroughtodeploymentandoperations.Considerembracingagilityifyouwanttoincreasethevelocityofachievingyouranticipatedbusinessoutcomes.Forexample,youcouldformateamtoinitiateaprojectand,withlimitedanalysis,useAWSservicestocreateaproofofconcept(POC).IfthePOCissuccessful,youcontinue.Ifnot,youselectadifferentapproach.TheAWSplatformcreatesalowbarrierforexperimentation,andallowsyoutorapidlydeployservers.WhenyoucompleteyourPOCexperimentyoucanshutdowntheAWSservicesenvironment,andnolongerpayforresources.Whenyoursolutionisreadyforendusers(theminimallyviableproduct),youcangathertheusers’feedbackanduseittoinformprioritiesforfuturefeaturereleases.Bydocumentingthedifferentphasesofyourcloudjourneyasitprogresses,youcancreateacompletepictureoftheITenvironment.Considerstoringtheartifactsthatyoucreateusingincrementalexperimentationinthesourcecodemanagementsystemthatyouusetodayforstoringandrevisingyourapplicationcode.

YoucancompletetheprocessofdescribingabusinessneedandtransitioningitintoanITsolutionusinganiterativeapproach.Inaddition,youcanuseaniterativeprocesstoprovidedeliveryteamsenoughdetailsothatwhattheybuildprovidestheintendedoutcome.Figure2illustrateshowanITcapabilitymapstotheservicesthatdeliverthecapability.

Figure2:ExampleofArchitecturalMappingfromCapabilitytoService

Whenyouuseaniterativearchitecturalapproach,youcanfocusmoretimeonbusinessneedsandgoals.Asbusinessneedschangeandmoreinformationissurfaced,thetechnicalarchitectureyouusetodeliverthebusinesscapabilitytothecustomercanshifttomatchthebusinessneed.Youcanalsoiteratefaster,tryingoutnewthingstoseeiftheyworkwithminimalbarriertoentry,duetoutilitypricing.Theiterativeapproachmakesiteasiertorollbackchangesorstandupaparallelenvironmenttotestnewfeatures.

YoucanuseacombinationofAWSservicestocreateITcapability,andusetheAWSServiceCatalogtocentrallymanagecommonlydeployedITservices.YoucanalsouseAWSservicesthatprovideaspecificITcapability,suchasAmazonGlacierfordataarchiving.

ThereareseveralcomponentstoconsiderfromthePlatformPerspective:

TheDesignArchitecturecomponent:Lookatthecommondesignpatternsusedinyourimplementationsandidentifycommonneedsandredundancies.

TheImplementationArchitecturecomponent:Lookatthesecurity,datahandlingandretention,logaggregation,monitoringneeds,andcommonoperationalpatterns.

TheArchitectureOptimizationcomponent:Identifyyouroptimizationstrategies,

whattoolsandprocessesneedtobechanged,andwhatautomationcanbeused.

DesignArchitecture

TheDesignArchitecturecomponentofthePlatformperspectivepromotestheengagementofstakeholdersfrommanypartsoftheorganization.Inyourcloudadoptionscenario,youneedtoprovidedifferentviewsonyourarchitecturetoeachstakeholder.Forexample,asyouworkwithbusinesssponsorstodesignasolutionyoucancontextualizethearchitecturetodescribehowITcanbeusedtoachievetheexpectedbusinessoutcome,andwhatthecosts,returns,andrisksmightbe.

PriortoanAWSadoptionjourney,yourorganizationshouldconsidermodifyingitsgovernanceandarchitecturalprinciplestoincludeAWSarchitecturalprinciples.Ifyouhavenotdoneso,thentryusingtheiterativemethoddescribedearliertoestablishtheseprinciples.Youcanbuildmethodologiesandprocessesusingsprints,justasyoubuildapplications.Asyoubuild,youcanvalidatethedesignofyourconceptualarchitecturesagainstyourgovernanceandarchitecturalprinciples.

ConceptualArchitectureActivity

Conceptualviewsaretechnicallyabstract,buttheyshouldbedescribedinacontextthatisfamiliartobusinessusers.UsetheconceptualarchitecturetodefinethebusinesscontextofanITsystemwithbusinessmodels.Thisiswhereyoubalanceshort-,medium-,andlong-termbusinessgoalsandconcernsforITinitiatives.

Threekeycomponentsofaconceptualarchitecturearebusinessvision,goals,andobjectives.Usetheconceptualarchitecturetounderstandwhichcapabilitieswillbeneededaspartofthelogicalorfunctionalarchitecturethatwilldescribethesolution.Figure3illustratesanexampleconceptualarchitecturethatdescribeswhereAWSservicesareapplicable.

Figure3ExampleofaConceptualArchitecture

UsingAWS,thecreationofaconceptualarchitecturecanbecomemoreiterative.YoucanuseAWSservicesaspartofthedevelopmenteffortbyusingexperimentationtovalidateandevolvetheapproach.Asbusinesscapabilityconceptsareproven,developmentteamscanstartworkondeliveringfunctionsandfeaturesintoproduction.Withquickerdelivery,end-userfeedbackcanbeusedtoverifywhetherbusinessobjectivesandcompliancerequirementsarebeingmetwiththecurrenttechnicalapproach.

Implementautomatedtestingtotestyourrapidlyiteratingconceptualarchitecture.Thisnotonlyminimizestheintroductionofbugsintoyourapplication,butalsoincludescontinuouscomplianceaspartofcontinuousdelivery,helpingtoensurethatchangestoyourapplicationdonotaffectyourorganization’ssecurityposture.

LogicalArchitectureActivity

Logical(orfunctional)architecturalviewsdescribethebuildingblocksoftheITsystemandtheirrelationshipswithoutgettingintothetechnicaldetailsofhowthefunctionalityisimplemented.Thelogicalarchitecturecontainsthedataflowandcapabilitymodelsthatrelatetothebusinessmodelsthatmeetthebusiness

outcomes.

Qualityattributes,dependencymapping,andplansforobsolescencecanbeidentified,documented,andaddressedaspartofdesigningthelogicalarchitecture.Alogicalarchitecture(Figure4)thatusesAWScanmakeuseofgeographicalduplicationaswellastheelasticnatureofAWSservices.Usingdesignprinciplesthattakeadvantageofthesecharacteristicswillallowsystemcapacitiestoexpandandshrinkasloadsexpandandcontract.

Figure4ExampleofaLogicalArchitectureDiagram

Youcanusedifferentapproachesbasedonthetypeofprojectyourorganizationisdesigning.Projectswithalongdurationtypicallyareusedinpredictable,repeatableenvironmentsorenvironmentswhererefinementofapproachisnotpossibleorrecommendedafterdecisionsaremade.Thesetypesofinitiativesaredrivenwithtop-downcontroloveroutcome.Anexampleofsuchaninitiativeisshuttingdownacorporatedatacenterafteradecisiontomovetothecloud.

Initiativeswithashortdurationaredrivenwithbottom-upfreedomoveroutcome.Changeindirectionisexpectedandmaybeencouragedforbetteralignmentwithshiftingbusinessneeds.

Therearealsohybridapproachestoinitiativeswherethegoalistomigrateanddecomposeamonolithicmission-criticalsolutionorenvironment.Theseinitiativeswillcombinethebestaspectsofheavyup-frontplanningwiththefreedomtoinnovateasneededtodeliveroptimizedcustomeroutcomes.

Considerations

?Dousefeedbackfromdeliveredfeaturestoreviewandrevisetheconceptualarchitecturewiththebusinessteam.

?Dominimizethenumberofarchitecturalprinciplestoallowthegreatestflexibilityinsolutiondevelopment.

?Dostayfocusedoncustomeroutcomesandbusinessobjectivesratherthantechnicalsolutions.

?DoexperimentwithAWSservicestoexperience,learn,andprovethatyourlogicalarchitecturewillachievethedesiredbusinessoutcome.

?Dofocusonshortdurationprojectscopinganditerativeprocessesforsystemsofinteractionwhereoutcomesaremorefluid.

?Doconsiderthepracticeofcreatinglogicalarchitectureasadynamicprocess.?Dolimittheamountofredundanttechnologiestoprevent“technologysprawl”andallowforfocusandspecialization.

?Donotmakefunctionalandimplementationarchitecturesdependentonacompleteconceptualarchitecture.Consideridentifyingakeyobjectiveandstartingdesignanddeliveryofthatfunctionality.Usethefeedbackfrom

adoptionofthefeaturesasinputintheevolutionoftheconceptual

architecture.

?Donotattempttocreatetheperfectarchitectureupfront.Considerstartingwiththehighestrisk/rewardscenarioanduseexperimentationtoproveyourapproach.

ImplementationArchitecture

TheImplementationArchitecturecomponentoftheAWSCAFPlatformPerspectivedescribesthedetaileddesignswithintheITsystemandthespecificimplementationcomponentsandtheirrelationships.Thisarchitecturealsodefinestheimplementationofthesystem’sbuildingblocksbysoftwareorhardwareelements.

TheimplementationarchitectureforanAWSenvironmentdescribesthedesignofthetechnicalenvironment.Thedescriptionisbrokenintolayers,witheachlayerprovidinginformationforaspecificteamintheorganization.AWSreferencearchitecturesareavailableathttp://./doc/ac5a9c04d15abe23492f4db3.html/architecture.Figure5illustratesahigh-levelimplementationarchitecture.Thisartifactworksbestonline,whereyoucanenableclickingoneachitemformoreinformation,andyoucanplanforautomaticupdates.

Figure5ExampleofanImplementationArchitecture

DescribingtheAWSenvironmentandprovidingguidanceonusagewillbeacriticalportionoftheimplementationarchitecturedevelopment.Describinghowresources,accounts,andtaggingwork,andthehowtheAmazonVirtualPrivateCloud(VPC)environmentisconfiguredprovidesinformationthatwillhelptheorganizationdeterminewhichresourcesareconsumedbyvarioussystems,applications,andinitiatives.

TheInformationArchitectureshouldsetstrategiesfordeployment,monitoring,auditing,andloggingthatwillgiveyouexposuretonearreal-timedata.Set

security,dataretention,gateway,androutingstrategiesandpoliciessoyourdeliveryteamshavetheinformationtheyneedtoenablecontrolovertheAWSenvironmentasitgrows.

Includetaxonomyandnamingconventionsaspartofthemetrics,monitoring,andchargebackimplementation.Theactualrunningenvironmentwillchangecontinuouslyandwillbebestviewedthroughdashboardswithnearreal-timeinformation.

Dashboardinformationcanberepresentedgraphicallyorbyusinglists.Ifyouuseagraphicaldashboard,userscouldclickthegraphictoshowadditionaldetail.Ifyouusealistinyourdashboard,usersfamiliarwithspreadsheetscanfindinformationinwell-definedcolumns.Figure6showsagraphicaldashboardthatcanprovidenearreal-timeinformation.

Figure6ExampleofaGraphic-basedNearReal-timeDashboardConsiderprescribingataxonomyandnamingconventionintheimplementationarchitecture.ThenyoucanimplementthistaxonomyasataggingstandardonAWSresources.Toincreaseconfidenceandreducerisk,youcanleveragetheAWSenvironmentduringimplementationarchitecturecreation.WhenyouuseAWS,theenvironmentcanbecreatedandtestedforverificationorcertificationearlierinthereleasecycle.Additionally,toolsareavailablethroughAWSandthe

AWSMarketplacethatcanautomateprocessesandshortenthetimeneededtodeliver,test,andoperateAWS-basedenvironments.

Defininganoperationalplaybookforhowyouaregoingtodeployandoperateyoursystemswillhelpensureconsistencyandrepeatabilityofsuccess.Thisplaybookshouldalsobeiterativeinnature,withtheconstructivefeedbackimplementedinsystemsthatdidnothavethiscapacityatthetimeofcreation.Considerations

?DoidentifyanetworkconnectivitystrategyforAWSservices.

?DooutlineAWScomponentstobeused(services/features).

?Dodefinesecuritycontrols(nativevs.third-partytools).GreaterdetailsareavailableintheAWSCAFSecurityPerspectivewhitepaper.

?Dodefinedatasecurityandretentionpolicies(encryption,backups,snapshots,third-partytools).

?Docreateandworktowardanautomateddeploymentprocesstoreducetheimpactofhumanerrorandintroduceportability.

?Docreateanoperationalplaybook.MoreinformationonthistopicisavailableintheAWSCAFOperationsPerspectivewhitepaper.

?Dooutlineamonitoringstrategy.

?Dooutlinealoggingstrategythatvalidatesthatyourloggingsystemcanmanagetheamountofinformationyoudecidetocollect.

?Docreateastrategyforresourcetrackingaspartofyourimplementationarchitecture,ensuringthatresourcesareappropriatelytaggedatthetimeofdeployment.Thiscanalsobeextendedintocostallocationtagging.

?Donotletapplicationenvironmentsforminanadhocfashion.Chooseastrategytoorganizeyourapplicationenvironments.

ArchitectureOptimization

TheArchitectureOptimizationcomponentoftheAWSCAFPlatformperspectivepromotestheadaptabilityofanarchitecturethatusesAWS—asbusinessneedschangeandasnewandbettertechnicalsolutionsbecomeavailable,yourarchitecturaldecisionscanbemodifiedandadjusted.Sincephysicalcomputersarenotpurchased,thelonglead-timeforprocurement,staging,burn-in,andconfigurationisnolongernecessary.Becauseyoucancontinuetooptimizeyourarchitectureduringthedesignphase,thisprocesscancompletedwithlessup-frontinformation;yourdecisionscanchangeandbeimplementedasneeded.

AsyouadoptAWSservices,akeyfocusshouldbeonbuildingtacitknowledgeintheorganization.Creatingacentralizedrepositorywithprinciples,patterns,bestpractices,aglossary,andreferencearchitectureswillhelpensuretherapidgrowthofAWSskillsintheorganization.Asyoustartanautomatedandagiledeploymentprocess,thecentralizedinformationrepositoryallowssystemsandpeoplewhodeployapplicationstoaccessthegoverningprinciplesaswellasthepiecesandpartsthattheyown.

CloudDesignPrinciplesandPatternsActivity

Adherencetothesoftwaredesignprinciplesandpatternsthatyoudocumentwillimprovequalityandproductivityandreduceriskduringsolutiondevelopment.Alldeliveryteamscanfollowtheseprincipleswhendesigningandbuildingsolutions.Apatternisaprovenapproachtoachievingaresult.Youcanautomatepatternsthatyouusefrequentlytoimproveefficiency,consistency,reliability,andsupportability.Considerfollowingthesebestpractices:

?Provideguidancethatcapturesreusableapproaches,leveragesaninfrastructureascodeapproach,andtreatsthatcodelikeapplicationcode(sourcecontrol,codereviews,etc.).

?Createabaselineoflanguageandunderstandingacrossthetechnicalorganizationtoeasecommunications.Thismightincludecreatingataxonomyandadictionaryoraglossarydescribinghowthingswillbenamedand

organized.

?Educateeveryonetoafoundationalleveltoprovidecommonlanguageandunderstanding.BuildingfluencyinthelanguageofAWScloudadoptionandexplainingthetaxonomyandnamingconventionswillhelpaccelerate

familiaritywithandabilitytousecloud-basedtechnologiesandapproachesacrosstheorganization.

?Usefasttrackorfactoryprinciplestocreatecommonapproacheswithreliableresults.Providedocumentationthatdescribesdiagrams,namingconventions,codereviewguidance,andsoontoprovideacommonlanguage,approach,andexpectations.Usingwiki-basedtoolsfordocumentationwillallowteamstoupdatedocumentationandkeepitcurrent,andwillprovideasingleauthoritativesourceforguidance.

?Createagovernanceprocessand/orteamthatensuresand/orauditstheoutcomeofpatternsandintendedresults.

?Providean“Andoncord”forthedeploymentteamtouseiftheyseesomethingthatdoesn’tfitinwiththeirunderstandingofpatterns.ApplicationMigrationPatternsActivity

ProvenapproachesformigratingITsystemstothecloudareavailableasmigrationpatterns.

Considerorganizingapplicationsinawaythathelpsidentifyandintroducepatternsthatyoucanusewithpredictableresults.Twoofthemorecommonlyusedpivotsarebusinesscriticalityanddataclassification.Understandingwhichcategoriesofdataareassociatedwithwhichapplicationswillprovidevaluableinsight.Anotherusefulpivotislevelofmissioncriticality.Dependingonyourneeds,youcouldalsoconsiderorganizingbysystemsofrecordversussystemsofinteraction,monolithicapplicationsversushighlydecomposedapplications,ornewapplicationsversusapplicationsneartheendoflife.

Oneapproachthatyoucantakeistoorganizeyourapplicationsintofivegroupsbasedontheactionyouwanttoplanforeachapplication.Thedifferentactionsincluderetiring,retaining,replacing,re-hosting,refactoring,andrewriting.Figure7illustratesthisfive-groupapplicationmigrationpattern.

Figure7GraphicRepresentationofanApplicationMigrationPattern

Youcanalsouseaninventoryofcurrentdatacenterapplicationsandtheirdependenciestodeterminewhichapplicationstomigrateandwhen.Thiscouldpotentiallyallowyoutoavoidacostlyequipmentrefresh,pushingawayfromcapitalexpenditure(CapEx),andtakingadvantageofAWSutilitypricing.

Formakingdecisionsaboutwhichpatternstoleverage,considercreatingaCenterofExcellence(CoE)teamtoselectpatternsthatenabletheshortesttimetovalue.Anotherapproachistoorganizeandprioritizebyeaseofefforttomigrate.Forexample,youcoulddecidetomigratedevelopmentandtestapplicationsfirst,followedbyself-containedapplications,customertrainingsites,pre-saledemoportals,andtrialapplications.Duringthemigration,considerprioritizingaTier1applicationtogainvisibilityandendorsementfromexecutivesponsors.

ConsiderdevelopingnewapplicationsorrefactoringexistingapplicationsintheAWSenvironment.Forexistingapplications,youcouldmigrateapplicationstotheAWScloudenvironmentandprioritizereworkoroptimizationinitiatives.TherefactoringcanbeenabledbytheagilityofdeploymentonAWS.

Considerations

?Doconsidernewapplicationsformigrationfirst.

?DostartdevelopmentofnewcapabilitiesorrewritesofexistingcapabilitiesintheAWSenvironment.

?Dotakeadvantageofcapacityconcernsasareasontoprioritizedevelopmentinthecloud.

?Doconsiderusingcodereview(bothforapplicationandinfrastructurecode)toprovideafeedbackloopthatimprovesprocessandreducestechnicaldebt.?Doconsiderusingwikistoprovideaccesstoguidancethatcanbeupdatedandmaintainedovertime.

?DoleverageAWScloudadoptionasawaytofasttrackmaturityofcombinedrolesandskillsthinking.Thiswouldmanifestasa

developer/security/operationsmindsetandcodingarchitecturalmodelstovalidateapproach.

?DouseAWScloudadoptiontoinstitutionalizeascalable,service-orientedarchitecture(SOA)approachtoseparateconcernsandtoenableintegrationofreusableservicesandlimittheamountofcodemaintained.

?Docreatepatternsthatassumefailurebybuildinginrecoverycodewithfeaturessuchascircuitbreakerpatterns,caching,andqueuing,and

exponentialback-off.

?DowritecodewithaneyetowardsreusethroughexposedAPIendpointsforeasydiscovery,integration,andreuse.

?Dointroduceyourdeploymentteamtoyourdevelopmentteam.Empowerbothteamstofullyappreciatethebenefitsofscalableinfrastructureand

utilitypricing.

?Donotoptimizeasolutionbeforeitiswellarchitected.

?Donotstartmigrationswithoutoperationalprocessesdefined.Considerdefiningbackupandrecoveryguidanceasaninitialstepinamigrationeffort.?Donotmanuallymigrateallapplications.Considerusingautomationtoscaleandacceleratemigrationofapplications(migrationfactory).

?Donotwaittoautomatesomething.Ifyou’redeployingthesamethingtwicemanually,investthetimeinautomation.

CAFTaxonomyandTerms

AWScreatedtheCloudAdoptionFramework(CAF)