Eb ay i nc scaling the data tier scaling the data

Info iconThis preview shows page 1. Sign up to view the full content.

View Full Document Right Arrow Icon
This is the end of the preview. Sign up to access the rest of the document.

Unformatted text preview: 16 © 2 0 0 6 e B a y In c . eB ay ,I nc . Scaling the Data Tier Scaling the Data Tier: Overview • Spread the Load nc • Minimize the Work ,I – Limit in database work • The Tricks to Scaling . – Segmentation by function. – Horizontal splits within functions. eB ay – How to survive without transactions. – Creating alternate database structures. 18 © 2 0 0 6 e B a y In c . Scaling the Data Tier: Functional Segmentation • Rationale ,I nc User hosts Item hosts Account hosts Feedback hosts Transaction hosts And about 70 more functional categories ay – – – – – – . • Segment databases into functional areas eB – Partitions data by different scaling / usage characteristics – Supports functional decoupling and isolation 19 © 2 0 0 6 e B a y In c . Scaling the Data Tier: Horizontal Split • Split databases horizontally by primary access path. nc – Write Master/Read Slaves – Segmentation by data; Two approaches . • Different patterns for different use cases ,I • M o d u lo o n a k e y , ty p ic a lly th e p r im a r y k e y . Simple data location if you know the key • M a p to d a ta lo c a tio n ay Not so simple if you don’t. Supports multiple keys. eB Doubles reads required to locate data. SPOF elimination on map structure is complex. • Rationale – Horizontal scaling of transactional load. – Segment business impact on database outage. 20 © 2 0 0 6 e B a y In c . Scaling the Data Tier: Logical Database Hosts nc . • Separate Application notion of a database from physical implementation • Databases may be combined and separated with no code changes • Reduce cost of creating multiple environments (Dev, QA, …) Rules CATY 1..N User Account Feedback Misc API SCRATCH eB ay Attributes Catalogs ,I A p p lic a t io n S e r v e r s DB1 DB2 DB3 21 © 2 0 0 6 e B a y In c . Scaling the Data Tier: Minimize DB Resources • No business logic in database nc . – No stored procedures – Only very simple triggers (default value population) ay – Referential Integrity – Joins – Sorting ,I • Move CPU-intensive work to applications eB • Extensiv...
View Full Document

This note was uploaded on 10/11/2012 for the course INFORMATIO IS taught by Professor Various during the Spring '11 term at CSU Northridge.

Ask a homework question - tutors are online