Web Form Automation for Bonterra Impact Management (fka Social Solutions Apri...
Designing Role-Based Database Systems to Achieve Unlimited Database Scalability
1.
2. Session Code: DAT451
Designing Role-Based Database
Systems to Achieve Unlimited
Database Scalability
Fernando G. Guerrero
CEO
Solid Quality Mentors
2
4. The "unpredictable workload" case
Millions of copies of a win app around the
world
All of them waiting for file safety, before using
them
At undefined times
Unlimited number of potential files to check
Unpredictable level of workload at any date and
time
Unpredictable geographical distribution of workload
Potentially, millions of requests per hour
Can we solve it?
6
5. The "unreasonable scalability" case
The system already reached its limits
They need to support workload 50 times higher
Scaling up is not an option
Scaling out is not a simple task
They need to support over 15K transactions per
second, with textual based data
Can we solve it?
7
6. Introductions
Fernando G. Guerrero
CEO of Solid Quality Global LLC, USA
President of the SolidQ subsidiaries around the World
fguerrero@solidq.com
Microsoft Regional Director for Spain since 2004
SQL Server MVP from year 2000 till 2007
Usual suspect at many international conferences
8
7. The SolidQ recipe
4 SQL Server MVPs old
friends speaking at a
conference in Palm Springs
A pleasant dinner at a nice
restaurant
2 bottles of my favorite
Spanish wine
1 bottle of a great single
Malt Whisky
Lots of honest and trustful
9
work for 6 years
9. This session is about…
Lesson learned from “unreasonable” and
amazing real systems from real enterprise
customers
Based on actual work performed by our Solid
Quality mentors
Learning to think out of the box when designing
DB systems
Thinking first, acting later
11
10. This session is NOT about…
Code
Demos
Obscure trace flags and registry hacks
Any particular commercial product or service
offering
Description about standard scalability
techniques
12
16. If you don’t need to buy
anything to implemnent a
solution, it does not mean that
this is the cheapest solution
18
17. Role based DB system design
A single box might be sufficient
Different tasks might imply different roles
Roles might be incompatible
You’ll never know until you measure it
19
19. Role based DB system design
A single box might be sufficient
Different tasks might imply different roles
Roles might be incompatible
You’ll never know until you measure it
21
22. A common sense powered queue
Multi-layered server roles:
The Reader
The Writer
The Master Root
“Magic array” of virtual server names
Self updated definitions
Proprietary advanced hash-based checking
Local vs remote storage
24
24. The Reader role
Organized as a Readers tree with a Reader Root
at the top
Verifies signature of requested file
Replies to client with simple response:
Safe
Unsafe
Unknown
If unknown, checks parent Reader for further
information
Receives updates from parent Reader
26
25. The Writer role
Works as a Reader as well
Organized as a flexible array of Writers
Sends signature to the Master Root
and sends file asynchronously if necessary
Replies immediately to client with simple
response:
Safe
Unsafe
Unknown
Receives updates from Distributor
27
26. The Master Root
Stores new files and signatures
Calls the qualification engine to qualify new
files
Distributes updates to root Reader
Distributes updates to array of Writers
28
39. Resources for IT Professionals
www.microsoft.com/teched
Tech·Talks Tech·Ed Bloggers
Live Simulcasts Virtual Labs
http://microsoft.com/technet
Evaluation licenses, pre-released
products, and MORE!
40. Related Content
Breakout Sessions (session codes and titles)
Interactive Theater Sessions (session codes and titles)
Hands-on Labs (session codes and titles)
Hands-on Labs (session codes and titles)