10,000 Tables Can?t Be Wrong: Designing a Highly Scalable MySQL
Architecture for Write-intensive Applications by Richard Chart
Chose MySQL for performance and stability, and less important but
still there, experience and support. Support is becoming
increasingly more and more important.
Starting point: 1 appliance supporting 200 devices
Problem/Goal: Extensible architecture with deep host and app
monitoring, over 1000 devices with 100 mgmt points each
Distributed collection over a WAN, with latency and security
concerns
Current reality: several times the scale of the original
goal
Commercial embedded product, so they actually pay for the
embedded MySQL server
Future: The fundamentals are sound: next generation of the
product moves up another order of magnitude
Data Characteristics
>90% writes
ACID not important
Resilient to loss, because gaps in data do not …
[Read more]