mysql - How do you architect massive design db? -

this design question regarding massive db design. instance, if going build database hold 10 million users, how architect it?

my main curiousity things database replication, speed anything?

when building db of size, fields "username" "name" "company" "dob" "gender" other making 1 table, on scale else should considered? indexes?

10 million not particularly huge, it's large enough should consider options carefully.

replication can - lot. assuming you're reading users table lot more you're writing it, might consider master database handles writes. reads application come 1 of n slave boxes.

indexes massively important, of course. you'll want indexes on columns searched (either in clauses, or result of relationships other tables (read: joins)). has been written how analyse sorts of queries application makes, , how smartly define indexes based on analysis. if you're learning stuff, go reading, , come more focused questions.

beyond single-master replication (and careful indexing), start big, might start thinking partitioning -- that's i've ever read about, don't want it.