If previous reports of iTunes music store sales lulling were worrying analysts, they've got nothing to worry about now –– the iTunes store sales have more than quadrupled during the Christmas season, according to a report made by E-Commerce.

People using their iTunes gift cards and new iPod users recieved from Christmas generated so much traffic, the service was significantly slower than usual, sometimes unavailable at times. People began posting help messages on Apple's forums, complaining that the iTune store could not be visited.

Originally, the problem was unclear as people were reporting the incidents of the unavaiability of the store. It soon became clearer as the possibility of increased traffic was examined.

I think that traffic for the iTunes store is more affected than other online music stores, and there's a good reason: people buying digital music players as presents for their friends/family often are ignorant of the smaller-brand players. The iPod is so well established, it's the device that desperate parents often turn to in the situation of uncertainty of a gift they should give their teenage kid.

So, what does this mean for competitors? Well, if they want to aim for the Christmas crowd, they're going to have to start appealing for consumers other than teenagers. That means that flashy designs are not as critical as solid marketing and making people believe that this is really the best device they can buy.

I'm interested to see how the digital music player market ends up next year, when Christmas isn't a determining factor...

Dani AI

Generated

and highlighted two linked themes: seasonal pressure on infrastructure and the role of reputation in purchase decisions. The notes below keep to practical, verifiable steps rather than speculation and separate advice for three groups: operators, competitors/device makers, and people affected by temporary service problems.

For operators: design for graceful degradation and test for real peak patterns. Use a global CDN for static assets, keep download hosts separate from transaction/authorization services, and make web tiers stateless so they can scale horizontally. Cache catalog reads and use read replicas for databases. Isolate payment and licensing flows (own autoscaling groups and third-party gateways), place non‑critical work behind queues, and add circuit breakers to protect core systems. Run realistic load tests, pre-warm caches, automate rollbacks/feature flags, and publish a clear status page plus ready-made customer messages to reduce support load during incidents.

For competitors and device makers: reduce friction and show visible trust signals. Provide simple, documented ways to migrate libraries, make cross‑platform playback easy, use familiar payment options, show clear warranty/privacy info, and work with retail partners to be visible during peak shopping periods. Those practical conveniences often matter more to gift buyers than purely cosmetic differences.

For users and post‑incident process: when access is spotty, consult the service status page and update the client before retrying; try a different device or network and save receipts or confirmation emails for support. After an outage, operators should publish a concise post‑mortem with root cause, impact, and remediation steps to rebuild confidence.

I know another bonus that iTunes had that others didn't is that its reputable.

I dunno about anyone else, but my folks arn't the type that throw credit card numbers to obscure websites, and I think that's partly the issue here.

Be a part of the DaniWeb community

We're a friendly, industry-focused community of developers, IT pros, digital marketers, and technology enthusiasts meeting, networking, learning, and sharing knowledge.