1 / 8

A Highly Reliable Fault-tolerant Airline Reservation System

A Highly Reliable Fault-tolerant Airline Reservation System. Zoheb Sait (zs29) Sandeep Varma (sv83). Software. Platform:ASP.NET Programming Languages:C# & VB Database Server:MS SQL Server 2000 Group Communication System:Spread. Architecture. Prototype used: Two Web Servers

amie
Download Presentation

A Highly Reliable Fault-tolerant Airline Reservation System

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. A Highly Reliable Fault-tolerant Airline Reservation System Zoheb Sait (zs29) Sandeep Varma (sv83)

  2. Software • Platform:ASP.NET • Programming Languages:C# & VB • Database Server:MS SQL Server 2000 • Group Communication System:Spread

  3. Architecture Prototype used: • Two Web Servers • Two Database Servers • Single Load Balancer • -- Easily Scaleable

  4. Failover • Database level: • Reads from any database server • Synchronous writes to all database servers through Spread • Transparent Failover • Auto-Reconfiguration and synchronization into group on recovery • Application Server level: • Load Balancer maintains list of available web servers • LB does transparent redirect of offline web server load to available web servers

  5. Processes • The database replication is provided by a process named ‘SpreadListener’ a daemon which runs as a windows service • ‘HeartBeatMonitor’ provides transparent fail-over to available database servers • ‘Load Balancer’ distributes clients requests in round-robin manner, and provides transparent web server fail-over

  6. Performance Tests Test: 500 users connecting in intervals of 2 sec in 5 users batch at a time Case 1: Replication Disabled v/s Enabled • Average Response time was 74ms with replication enabled • Average response time was 51ms with replication disabled

  7. Performance Tests Case 2: LB and Replication v/s No LB and Repl • Average Response time was 51ms with load balancing and replication disabled • Average Response time dropped to 19ms with load balancing and replication.

  8. Application Stress Test • With replication disabled: • ~200 errors • With replication enabled: • ~400 errors • Maximum number of concurrent transactions without failure: • ~ 60 transactions/per sec without a load balancer • ~ 90 concurrent transactions per/sec with a load balancer

More Related