This could cause problems to arise over the course of the migration. Secondly, all of Musify’s data had been stored in one bucket with GCP, although the data comprised three different types of objects, each type being a different size. Segmenting parts of the data in this way inherently made the project more complex than moving all of the data in its entirety. First, Musify had many outdated objects that the company didn’t need to pay to move, so they provided a list of files to Flexify.IO for the migration project. Musify had several unique needs that required a tailored approach. After contemplating the technical and logistical challenges of doing this migration himself, Liu discovered Flexify.IO through a Google search. Not only would storage and egress costs be greatly reduced, but also network performance would be improved for Musify customers.
Liu discovered that migrating his data to Backblaze B2 in the U.S., while taking advantage of their partnership with the content delivery network offered by Cloudflare, would save him about 80% over what he was spending with GCP.
Predictably, the costs to store and move all that data began to skyrocket. At the same time, Musify’s customer base was expanding beyond Japan to include Latin America, Europe and beyond, introducing latency issues to the equation. As Musify grew and required more and more storage, the volume of stored data reached over 500TB rather quickly. When CEO David Liu launched Musify, he chose Google Cloud Platform (GCP) in Tokyo as its cloud service provider. Flexify.IO has shared a case study which describes how Musify, a streaming music service provider based in Japan, used Flexify.IO to achieve 80% cost savings and improved performance.
0 kommentar(er)
