The document summarizes Cocolog's migration from PostgreSQL to MySQL. Cocolog is a blogging platform operated by NIFTY Corporation, one of Japan's largest internet service providers. It experienced rapid growth and faced scaling issues with PostgreSQL. The migration involved carefully partitioning user data across multiple MySQL servers for improved performance and high availability. Key steps included writing user metadata to a global MySQL database, migrating each user's data asynchronously, and configuring new users to specific user partitions.
The document discusses testing the upload of slides to Slide Share using its API. It mentions uploading a test and test_2, and asks if the uploads were OK or NG (No Good).
The document summarizes Cocolog's migration from PostgreSQL to MySQL using database partitioning. It discusses:
1) Cocolog's history and growth requiring a migration for scalability.
2) The database partitioning strategy involving writing global user data to one database and user data by partition to other databases.
3) The steps of the migration including moving user and non-user data asynchronously to the new partitioning scheme.
The document summarizes Cocolog's migration from PostgreSQL to MySQL. Cocolog is a blogging platform operated by NIFTY Corporation, one of Japan's largest internet service providers. It experienced rapid growth and faced scaling issues with PostgreSQL. The migration involved carefully partitioning user data across multiple MySQL servers for improved performance and high availability. Key steps included writing user metadata to a global MySQL database, migrating each user's data asynchronously, and configuring new users to specific user partitions.
The document discusses testing the upload of slides to Slide Share using its API. It mentions uploading a test and test_2, and asks if the uploads were OK or NG (No Good).
The document summarizes Cocolog's migration from PostgreSQL to MySQL using database partitioning. It discusses:
1) Cocolog's history and growth requiring a migration for scalability.
2) The database partitioning strategy involving writing global user data to one database and user data by partition to other databases.
3) The steps of the migration including moving user and non-user data asynchronously to the new partitioning scheme.