Tags: data migration*

0 bookmark(s) - Sort by: Date ↓ / Title /

  1. Yahoo is executing a massive migration of 500 petabytes of email infrastructure and platform workloads to Google Cloud. This strategic move aims to replace rigid on-premises legacy architecture with agile cloud services, addressing previous bottlenecks that caused feature deployment delays lasting up to two years. By adopting an iterative co-development model rather than traditional waterfall planning, Yahoo is increasing its operational efficiency and freeing engineering teams from routine hardware maintenance.

    * Migration of 500 petabytes of data to Google Cloud while maintaining continuous service for hundreds of millions of users.
    * Transitioning from rigid on-premises infrastructure to a flexible cloud environment that allows for rapid testing and simulation.
    * Accelerating the deployment of advanced features, such as AI-powered productivity tools, by leveraging specialized GPU and machine learning resources.
    * Shifting engineering focus from manual server patching and hardware upkeep toward product innovation and development.
  2. 37signals is finishing its move from AWS to on-premise infrastructure, expecting to save $1.3 million per year in operating costs after completing the project. The company initially moved compute workloads in 2024 and is now migrating data from S3, with AWS waiving $250,000 in egress fees. Overall infrastructure costs are projected to fall from $3.2 million to under $1 million annually.

Top of the page

First / Previous / Next / Last / Page 1 of 0 SemanticScuttle - klotz.me: tagged with "data migration"

About - Propulsed by SemanticScuttle