building a scalable architecture for web apps.ppt

BuildingaScalableArchitectureforWebApps-PartI(******@Directi)ByBhavinTurakhiaCEO,Directi(p://wiki.|http://careers.)mercial1AgendaWhyisScalabilityimportantIntroductiontotheVariablesandFactorsBuildingourownScalableArchitecture(inincrementalsteps)VerticalScalingVerticalPartitioningHorizontalScalingHorizontalPartitioning…-Meta-data>dataNumberofRequestsexponentiallygrowswithuserbaseRoR/Grails–-Numberofusers/sessions/transactions/operationstheentiresystemcanperformPerformance–OptimalutilizationofresourcesResponsiveness–TimetakenperoperationAvailability-ProbabilityoftheapplicationoraportionoftheapplicationbeingavailableatanygivenpointintimeDowntimeImpact-Theimpactofadowntimeofaserver/service/resource-numberofusers,ostMaintenanceEffortHigh:scalability,availability,performance&responsivenessLow:downtimeimpact,cost&mercialTheFactorsPlatformselectionHardwareApplicationDesignDatabase/DatastoreStructureandArchitectureDeploymentArchitectureStorageArchitectureAbusepreventionMonitoringmechanisms…mercialLetsStart…Wewillnowbuildanexamplearchitectureforanexampleappusingthefollowingiterativeincrementalsteps–InspectcurrentArchitectureIdentifyScalabilityBottlenecksIdentifySPOFsandAvailabilityIssuesIdentifyDowntimeImpactRiskZonesApplyoneof-mercialStep1–LetsStart…Appserver&mercialStep2–VerticalScalingAppserver,mercialStep2-VerticalScalingIntroductionIncreasingthehardwareresourceswithoutchangingthenumberofnodesReferredtoas“Scalingup”theServerAdvantagesSimpletoimplementDisadvantagesFinitelimitHardwaredoesnotscalelinearly(diminishingreturnsforeachincrementalunit)RequiresdowntimeIncreasesDowntimeImpactIncrementalcostsincreaseexponentiallyAppserver,mercialStep3–VerticalPartitioning(Services)AppServerDBServerIntroductionDeployingeachserviceonaseparatenodePositivesIncreasesperapplicationAvailabilityT