• Share
  • Email
  • Embed
  • Like
  • Save
  • Private Content
GigaSpaces Scalability Live Demo
 

GigaSpaces Scalability Live Demo

on

  • 1,946 views

Experience how XAP scales web servers based on load. Learn how our In-Memory Data Grid performs automatic recovery when a machine failes.

Experience how XAP scales web servers based on load. Learn how our In-Memory Data Grid performs automatic recovery when a machine failes.

Statistics

Views

Total Views
1,946
Views on SlideShare
1,624
Embed Views
322

Actions

Likes
0
Downloads
31
Comments
0

5 Embeds 322

http://cloud.gigaspaces.com 292
http://cloud-stg.gigaspaces.com 25
http://localhost 3
https://cloud.gigaspaces.com 1
http://static.slidesharecdn.com 1

Accessibility

Categories

Upload Details

Uploaded via as Microsoft PowerPoint

Usage Rights

© All Rights Reserved

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
    Processing…
Post Comment
Edit your comment

    GigaSpaces Scalability Live Demo GigaSpaces Scalability Live Demo Presentation Transcript

    • GigaSpaces Scalability Live Demo
    • In this Demo
      • Experience automatic scaling based on request throughput
      • See how the application fails over and auto-recovers after failure
    • How to Experience Automatic Scaling
      • Deploy the demo on the cloud
      • Study the demo architecture
      • Web auto-scaling (requests/sec threshold)
      • Automatic failover and auto-recovery
      • STEP 1 –
      • DEPLOY THE DEMO ON THE CLOUD
    • How to Experience Automatic Scaling?
      • Click Deploy
      • Click Refresh Status
      • Wait until application status =
      Deployed Expected waiting time: ~7 min In the meantime let’s study the stock demo architecture…
      • STEP 2 –
      • STOCK DEMO ARCHITECTURE
    • Architecture – Processor Space
      • Stock feeder simulates stock price changes
      • Processor analyzes data as it arrives (price change delta)
      Processor (Code + Data) Write Data
      • Stock data exposed to web browser with AJAX
      Architecture – Embedded Web Server Web Load-Balancer http:// http:// Read Data (SQL Query), Get Statistics (Admin API) Write Data Processor (Code + Data)
    • Stock Application Home Page Stock data exposed via REST
    • Stock Application Home Page
      • Map/Reduce query via REST
    • Application Home Page – Statistics Space (data) statistics JVM statistics Web statistics
      • STEP 3 –
      • WEB AUTO-SCALING
    • How to Experience Automatic Scaling
      • Wait until application status =
      • Click View Stocks
      • Note the Web Requests/Second gauge
      Deployed
    • Web Container Auto-Scaling Load Balancer monitors web availability Web Web Load-Balancer
    • Web Web Web Load-Balancer Web Container Auto-Scaling A new machine is started when the requests-per-second threshold is breached
    • Increase Load – Auto-scale-out Click View Stocks twice A total of 3 “View Stocks” pages are open. Note that the gauge is above threshold.
    • Increase Load – Auto-scale-out Wait for a machine to start automatically.
    • Increase Load – Auto-scale-out When the machine starts, the number of web Processing Units (PUs) increases from 2 to 3
    • Decrease Load – Auto-scale-in Close 2 “View Stocks” pages (leave only 1 open) Note the gauge is below threshold
    • Decrease Load – Auto-scale-in Wait until a Web_Container machine is automatically terminated (scaling in back to 2 machines). This might take a few minutes
    • Step 3 – Recap
      • Increase load by starting additional web pages  Web server scales out
      • Decrease load by closing the additional pages  Web server scales in
      • STEP 4 –
      • AUTOMATIC FAILOVER AND
      • AUTO-RECOVERY
    • Automatic Failover of Data Grid Stock updates are replicated to backup Partition 1 Active Partition 2 Backup Partition 2 Active Partition 1 Backup Write Data Replication
    • Automatic Failover of Data Grid When a machine fails, backup becomes primary Partition 1 Active Partition 2 Active Partition 1 Backup Partition 2 Active Write Data
    • Automatic Recovery of Data Grid A new machine is started, backups are deployed Partition 2 Backup Partition 1 Backup Partition 1 Active Partition 2 Active Write Data Replication
    • Automatic Recovery of Data Grid Number of active instances is re-balanced Replication Partition 1 Active Partition 2 Backup Partition 2 Active Partition 1 Backup Write Data
    • Start the Monitoring Web Dashboard
      • Click Monitor to start the web dashboard
      • (works best with Firefox / Chrome)
      • Click Login (anonymous login)
    • The Processor Space (Web Dashboard)
      • Expand ProcessorPU
      • tree node.
      • Note each partition
      • Has a primary (green)
      • and a backup (blue)
      • instance.
    • Shut Down Machine
      • Switch back to the main screen,
      • and click the Shutdown button of one
      • Web_Container machine:
    • Failover (Web Dashboard)
      • Switch back to the Web Dashboard.
      • Note how Backup (blue) becomes Active (green)
    • Experience Machine Failover
      • Wait until a new machine is started and the Processor space rebalances.
    • Step 4 – Recap
      • Machine failure  New machine starts automatically A backup space instance takes over
      • Machine started 
      • New backup space started
      • Rebalancing of active instances.
    • What This Demo Illustrated
      • Automatic scaling of the web application based on load
      • Automatic recovery from machine failures