“This post contains common different methods of functional
partitioning and common considerations for database setup and
capacity. In any case, design or company DBAs, developers,
engineers and architects should consider the pros and cons of any
method of sharding or partitioning. In the end, compromises will
have to be made given the pros and cons of a system setup. Common
Considerations“I have seen many different database system setups and overall
architectures that span the full scope of centralization and
decentralization from a database perspective. In the typical Web
2.0 startup, it can be hard to determine what the systems will
actually do when brought live in production; that said, we have to
start somewhere and base our decisions on many factors. Some of
those factors are budget, horizontal and vertical scaling,
projected growth and projected usage based on trends and other
hypothetical information.“In any Web 2.0 company, you might face problems such as data
growth sprits, a massive influx of unpredicted usage either caused
by the users of the product or from an external source. In many
cases, I have found that good database and query design, proper
indexing and horizontal functional partitioning are the main keys
for success as a DBA.”
MySQL: Functional Partitioning
By
Get the Free Newsletter!
Subscribe to Developer Insider for top news, trends, & analysis