It is rare to be able to observe a system release failure this clearly in real time, so I have been watching what is happening at Ameblo. That said, there is not much official information, but judging by what can be inferred, the situation appears to be as follows.

(1) They decided to update the system in pursuit of better performance.
(2) They moved from a PHP-based system to Java. The OS/Web Server was migrated to
   Sun-ONE-Web-Server/6.1.
(3) The old blog-site addresses had the following format: http://example.ameblo.jp/
   They were changed to this form: http://ameblo.jp/example/
   *.ameblo.jp became an alias for ameblo.jp. All IPs are 202.213.214.164.
(4) The switchover was completed, but performance was terrible.
   The rankings, one of Ameblo’s main attractions (Ameblo awards prize money based on rankings),
   apparently do not include visitors to the portions operated under subdomains.
(5) Performance problems appeared from the initial release, but because they did not
   decide to roll back, the new site continued to be updated, and by now rollback is impossible.
(6) At present, they are carrying out performance tuning and other work while
   changing the system in the production environment.

Why did this happen? The reason seems obvious to me, but what do you think? Alternatively, what measures would you take?

Related posts

The 7 Laws of Identity—Seven Laws of Identity

Kim Cameron, who left Microsoft on May 5 this year(*1), formulated the “7 Laws of Identity (Seven Laws of Identity)” from discussions with the “Identity Gang.”…

Identity · 2011-05-31