《Building a Scalable Architecture for Web Apps》.ppt

Creative Commons Sharealike Attributions Noncommercial Building a Scalable Architecture for Web Apps - Part I(Lessons Learned @ Directi) By Bhavin Turakhia CEO, Directi ( | | ) Agenda Why is Scalability important Introduction to the Variables and Factors Building our own Scalable Architecture (in incremental steps) Vertical Scaling Vertical Partitioning Horizontal Scaling Horizontal Partitioning … etc Platform Selection Considerations Tips Why is Scalability Important in a Web 2.0 world Viral marketing can result in instant successes RSS / Ajax / SOA pull based / polling type XML protocols - Meta-data data Number of Requests exponentially grows with user base RoR / Grails – Dynamic language landscape gaining popularity In the end you want to build a Web 2.0 app that can serve millions of users with ZERO downtime The Variables Scalability - Number of users / sessions / transactions / operations the entire system can perform Performance – Optimal utilization of resources Responsiveness – Time taken per operation Availability - Probability of the application or a portion of the application being available at any given point in time Downtime Impact - The impact of a downtime of a server/service/resource - number of users, type of impact etc Cost Maintenance Effort The Factors Platform selection Hardware Application Design Database/Datastore Structure and Architecture Deployment Architecture Storage Architecture Abuse prevention Monitoring mechanisms … and more Lets Start … We will now build an example architecture for an example app using the following iterative incremental steps – Inspect current Architecture Identify Scalability Bottlenecks Identify SPOFs and Availability Issues Identify Downtime Impact Risk Zones Apply one of - Vertical Scaling Vertical Partitioning Horizontal Scaling Horizontal Partitioning Repeat process Step 1 – Lets Start … Step 2 – Vertical Scaling Step 2 - Vertical Scaling Introduction Increasing the hardware resources without changing t