Scaling Data and Apps in the Cloud Data Masters

Special Thanks To… Rokk3r Labs Charles Irizarry & Charles Walter

Our Sponsor! Brian Nunez

 Short bio about me…  Andrew Simkovsky  15 years working with database technology  Oracle, MySQL/MariaDB, SQL Server, Postgres  Redis, MongoDB, CouchDB, Cassandra, Neo4j  Worked across many industries  Consulting, Retail, Telecommunications, Energy  Data, Marketing, Gaming, Health Care

DBTekPro

Let’s Get Started!

Scaling: What’s it really about?  User access to business logic and data  Either reading or writing, or both  Non-user access to business logic and data  Background data processing Scaling is making sure that this happens without flaw at all sizes and access volumes!

Cost Thresholds  Micro – light processing, simple activities, handful of users  Small – tens of users  Medium – hundreds of users  Large – thousands of users  Huge – heavy processing, diverse activities, lots of users

Cost Thresholds – The Old Way waste

Cost Thresholds – The Cloud Scaling Way

Scaling Different Layers  Network  Data storage  Application / functional logic  Presentation to user

Example: Word Processor (1 user)

Example: Word Processor (many users) PRESENTATION APPLICATION LOGIC DATA STORAGE

Scaling Needs for Different Layers  Network  Request volume  Traffic isolation  Geographical  Data storage  Possibly separate reads & writes  Separate bulk access vs individual  Complex data vs simple data  Static data vs changing data  Different types of database engines based on type of access

Scaling Needs for Different Layers  Application / functional logic  Separating application by functionality to create services  Each service can scale independently  Groups of simple services can create highly customized applications  Presentation to user  Web servers server only rendered pages  Leave logic to the application  Exception: real-time, user-facing functionality only needed by a single user within a session

Scaling Strategy Ideal Environment that simply evolves from one threshold to the next with minimal intervention or impact Next Best Environment that evolves from one threshold to the next with some impact, but is planned & controlled NOT ideal Hit limitations unexpectedly, causing outages, downtime, performance impact, and you are scrambling to fix it

Infrastructure as as Service “As A Service” Platform as a Service Software as a Service

Infrastructure as a Service  Amazon Web Services  Google Cloud  Microsoft Azure  Rackspace  OpenShift  Do It Yourself

IaaS Management Frameworks Management Frameworks Infrastructure as as Service Platform as a Service Software as a Service

IaaS Management Frameworks  AWS API  OpenStack  CloudStack  Euclayptus  Chef  Puppet  Ansible  SaltStack

Platform Service Providers  AWS Elastic Beanstalk  Google App Engine  Heroku  Cloud Foundry (Pivotal CF)  OutSystems  WaveMaker  Many others….

IaaS Management Frameworks Infrastructure as as Service Platform as a Service Software as a Service Management Frameworks PaaS Providers

PaaS Pros & Cons PROS:  Get started quickly  Very low initial cost  Little or no infrastructure knowledge needed  Performance metrics readily available  Can moderately scale easily Cons:  Lots of providers, difficult to choose  Some will not support all technologies  Little control over individual components  Switching from PaaS to self-managed can be tough

How do we put it together?

Example App Greeting Card Maker!!

Example App – Greeting Card Maker  Create, send, and receive custom greeting cards  Both web & mobile app front ends  Custom cards creator gadget  Manage contact lists & event calendar  Reminders of events  Notification of cards received & opened  Send “Thank You” responses  Online payments

Internal Needs  Store & manage data  User profiles  Contact lists  Personal event calendars  Storage for clip art, animations, other media  Interface to create greeting cards  Browser  Mobile app  Mechanism to render the final card as an animation  Mechanism to send notifications  Online payments  Application to handle all the logic

Conceptual User dataMultimedia Application BrowserMobile App Notifications

Micro Option 1 (traditional) All data (user + multimedia ) Application Browser Notifications Desktop or mobile All on single web server $3 - $40 / month No scaling Handful of users

Micro Option 2: PaaS (Heroku) Application Browser Notifications Desktop or mobile Heroku Container User Data Multimedia Caching $0 - $40 / month + add-ons Initial scaling Handful to hundreds of users

Micro Option 3: PaaS (Elastic Beanstalk) Application (EC2) Browser Notifications (SNS) Desktop or mobile Elastic Beanstalk Container User Data (RDS) Multimedia (S3) CloudFront $0-40 / month+ Initial scaling+ Handful to hundreds of users

Scaling Note… Micro Options 2 & 3 already enable you to scale from Micro to Small, and maybe to Medium!!

Moving On To Medium  Remember: Looking to minimize pain of crossing cost threshold  Let’s follow AWS path  Need thousands of users eventually  Need to ensure uptime  We get spikes of user activity  Holidays are especially tough!

Medium Option: AWS Application (EC2) Browser Notifications (SNS) Desktop or mobile User Data (RDS) Multimedia (S3) CloudFront $250 / month+ Hundreds of users+ EC2 c3.large x2 =$150 RDS t2.med x1 = $49 ELB = $18 SNS = $10 Transcoding = $10 Application (EC2) User Data (RDS) AZ1 AZ2 ELASTIC LOAD BALANCER

AWS Pricing Calculator

Large Option: AWS AZ1AZ2 AZ3AZ4 DB Applicatio n (EC2) CACHE HAProxy Applicatio n (EC2) CACHE HAProxy Applicatio n (EC2) CACHE HAProxy Applicatio n (EC2) CACHE HAProxy ROUTE53 Web Server

Further Scaling  Remember: Looking to minimize pain of crossing cost threshold  Get into the details per bottleneck  Inflate out: separation / specialization of functionality  Automation, automation, automation  Infrastructure components are cattle, not pets  Seek out new technology & tools

Questions?

Thank You For Coming! Please rate this Meet Up: (or go there to join!) Check out my blog and forums: