Inside Mac OS X Snow Leopard Server: Apple’s server strategy
October 13th, 2009
Daniel Eran Dilger
Years before Mac OS X 10.0 was first released in 2001, Apple launched Mac OS X Server, targeting its newly acquired Unix-based operating system technology at the education and workgroup server market. Apple has struggled ever since to find a broad server strategy that works. The solution may be as obvious as the iPhone App Store.
Apple accomplished something that many others in the industry failed to do: marry the power and familiarity of Unix with accessible ease of use in a commercially successful product. Ray Noorda tried to do this at Novell in the early 90s; Caldera’s OpenLinux also failed to take over the task from Novell ten years ago. United Linux and a series of followup attempts to standardize Linux all failed to accomplish their aims. A variety of efforts to sell Linux to consumers since then have all made very little progress outside of a small niche of hobbyist users.
Apple’s ability to successfully tame Unix, something it largely inherited from Steve Jobs’ NeXT and the years and tens of millions that went into creating what would eventually become Mac OS X at Apple, seemingly should have resulted in tremendous success for Mac OS X Server as well. But that never really happened.
Apple’s miserable server history: 1985 – 1998
Unlike NeXT, Apple never really managed a serious server business. In the mid 80s, Jobs originally had pushed Apple’s management to invest in aggressively selling the Macintosh to businesses following the model of the original Xerox Star machines which the Mac team had drawn many of its original design influences from.
Jobs envisioned a Macintosh Office, where Macs were networked with shared laser printers and file servers. That vision would prove to be well ahead of its time for the mid 80s; after being ousted from Apple, Jobs took his concepts to NeXT and built just that. His original NeXT Computer supplied advanced networking savvy, state of the art desktop laser printing, and delivered the server power of its underlying Unix foundation with ease of use that rivaled or exceeded the Macintosh.
Meanwhile, Apple leisurely shipped AppleShare software for turning a Mac into a dedicated file server; it attempted to shoehorn background services into what was really a simple appliance desktop OS that wasn’t really up to the task. The company also began selling A/UX, a version of Unix with some basic integration with the Mac System 7 desktop. Apple later partnered with IBM to deliver Apple-designed servers running AIX (IBM’s distribution of Unix), targeted as serving Mac clients in education. None of these efforts were taken very seriously.
When Apple acquired NeXT, the small niche of ‘powerful development tools on a Unix foundation’ that NeXT had struggled to assemble in its desperate plans to sell its advanced technology in some fashion ended up being associated with Apple’s own inability to deliver serious server gear or a coherent strategy. The customers NeXT had managed to collect mostly jumped ship, leaving Apple with the NeXT Curse: lots of great technology but no idea how to effectively market it.
Apple’s first plan was to simply drop NeXT’s advanced desktop operating system onto its Mac hardware and present its customers with a single huge upgrade: blazing performance, far greater reliability, powerful server and networking features, advanced development features, and much greater compatibility with foreign computer systems. The new system was code-named Rhapsody, to fit in with Apple’s series of music-related names for Mac OS releases, including the never released Copland and Gershwin as well as Harmony (Mac OS 7.6), Tempo (Mac OS 8), Allegro (Mac OS 8.5), and Sonata (Mac OS 9).
Mac users were suspicious of the new changes Rhapsody would bring, but Apple’s third party developers were furious. Such a plan would require a massive overhaul of their applications, with no guarantee that the new Mac platform would even sell. Their massive resistance resulted in Apple backpedaling to plan B. That involved spending several years merging existing Mac OS procedural development APIs into the new operating system so that existing legacy Mac code from Adobe, Macromedia, and Microsoft could continue to sell “as is” on the new system, with only minimal work from the developers.
It would end up taking nearly five years for Apple to ship a version of Mac OS X that could serve as its official replacement for the old Mac OS, which Apple continued to update and sell in the interim. At the same time, Apple almost immediately shipped the existing Rhapsody as Mac OS X Server 1.0, which was essentially NeXT’s operating system with a minor interface overhaul designed to make it look more like a Macintosh.
Mac OS X Server evolved into a “bonus package” of server tools applied to each new release of the desktop Mac OS X. Those server tools were aimed at managing groups of Macs and providing file and print services. At a time when the “Network Computer” was turning into a raging buzzword, Apple delivered NetBoot as a service of Mac OS X Server, which allowed administrators to boot up iMacs over the network using a single disk image.
Apple’s modern server strategies
Apple continues to sell Mac OS X Server, primarily to its education users, but has never managed to make much of an impact with its server operating system despite its being relatively easy to set up and use. In 2002, Apple debuted the Xserve as its return to selling dedicated server hardware. The new model made some impact in high performance computing but has never been a major part of Apple’s hardware revenues.
Given that Apple is now a major player in serving its own media store with iTunes, the world’s leading mobile software outlet in its App Store, manages a leading HD movie trailers video service, and serves up push messaging and cloud sync services to millions of paying customers, one might wonder why Apple’s own server products haven’t caught on better in the general market for server software.
Apple continues to develop consumer and workgroup server products in a variety of overlapping and complementary areas:
Mac OS X Server: Apple’s server package supplies core network services such as DNS, DHCP, web, file sharing and printing. Directory services supply a level of security and convenience for network services, providing users with secure single sign-on for everything they need to do, all without transmitting their actual passwords over the network.
Collaboration: Mac OS X Server has also expanded in recent releases to offer a series of new workgroup services: calendaring, contacts, wiki collaboration, and of course email and instant messaging. This package offers an alternative to Exchange Server and in some cases SharePoint, although many Exchange admins are quick to revile the product as not being identical in scale and scope to Microsoft’s offerings. Still, Apple’s product costs very little for a group of 100 users, while Microsoft’s popular alternatives quickly add up to cost tens of thousands of dollars.
Podcasting: A relatively new feature of Mac OS X Server, Podcast Producer, allows schools and companies to set up advanced workflows for digitally taping lectures and events and automatically submitting them to a server system that processes the video, adds corporate titling and video effects, and then distributes the finished product as podcasts via iTunes, QuickTime Streaming Server, or a local media library.
Xgrid: A key feature of Podcast Producer is its integration with Xgrid, Apple’s network distributed processing technology. Xgrid allows a company to set up client machines to accept tasks from the server when they are idle, which results in video processing at supercomputer speeds with zero additional hardware purchases.
Mac OS X Server suffers from a split personality that on one hand seeks to be point and click simple for Mac users, and on the other hand attempts to provide advanced users with a large degree of control. Most users will quickly graduate from the basic “Server Preferences” admin tool and want to dive into the more complex world of Server Admin, but the inherent complications involved with managing a server can overwhelm many Mac users expecting wide open flexibility and sheltered simplicity in the same package, at the same time.
Pro Apps: Apple’s server products have also meshed with the company’s Pro Apps. At the end of 2006, Apple acquired Proximity’s “artbox” products for video asset management, and released the technology as Final Cut Server early last year. The product doesn’t require Mac OS X Server, but can scale up from a workstation to a large installation running on server hardware.
Database: The company’s FileMaker subsidiary quietly makes workgroup database products that similarly don’t require Mac OS X Server, but can scale up from a desktop installation to a server-based network deployment.
Server hardware: Apple continues to sell its Xserve, and expanded its server offerings in designing a relatively low cost Fiber Channel RAID appliance in 2003; it discontinued the effort five years later to delegate its RAID storage sales to a partner.
SAN software: It continues to sell Xsan, a software product designed to allow multiple servers or clients to access a networked storage appliance at once as a local drive (called a “Storage Area Network”), rather than as a network file server; this allows for multiple servers to share the same storage pool and provides for advanced fallback, so that a server can fail and a secondary backup system can take over, reading the same storage (such as its email or database store) rather than requiring a backup recovery.
Cloud services: It has become fashionable to ridicule Apple for being behind in the scramble to announce “cloud services” initiatives, but Apple has been operating .Mac and its rebranded MobileMe to a population of a few million paying customers. The original rollout of MobileMe in tandem with iPhone 2.0 was flawed, but Apple quickly took steps to correct problems and has delivered competitive push messaging and online services that have expanded in innovative ways at regular intervals. The company added iDisk access to cloud files from the iPhone and iPod touch, and created new “Find my iPhone” messaging, remote lock and wipe features that very few other consumer mobile devices can claim.
Leveraging third party server support
Apple’s biggest problem with its server offerings may be that the company is trying to run the entire show. There are some third party server products designed for use with Mac OS X Server, including IBM’s Informix Dynamic Server for online transaction processing, or Oracle’s Database 10g product. Users are also free to install their own open source projects and develop their own custom server apps using the tools Apple bundles with Server, including Perl, PHP, Ruby and Rails.
What Mac OS X Server is really missing however is a third party ecosystem of supporting players who have a vested interest in selling the operating system. IBM and Oracle are supporting Mac OS X largely just to cover the bases. Apple lacks any real motivation for third parties to actually deliver server software solutions based on Mac OS X technologies.
That could change if the company adopts an iPhone App Store for its server platform, something the company is also expected to do for its desktop Mac platform. Currently, Apple bundles a variety of open source engines into Mac OS X Server and presents a cohesive administration interface for them with Server Admin, along with a dramatically scaled down admin tool called Server Preferences, which is designed for the entry level users with only the most basic needs.
This modular architecture could easily be retrofitted to support third party server applications simply by adding a download and configuration storefront adapted from iTunes. Open Source developers could customize existing products to integrate with Mac OS X’s directory services in order to inherit existing user accounts and permissions and to make it easy to secure the server using the existing interface in Server Admin for setting Service Access Control Permissions to limit administrative rights to individual server features.
Just as with the iPhone, this would instantly create a viable market for developing server applications on Apple’s platform. There are a variety of third party server opportunities that would sell Mac OS X Server along with Xserve hardware, but which Apple is unlikely to ever address on its own:
Phone PBX: Office telephony systems are notoriously expensive, but open source projects like Asterisk make it relatively easy to replace dedicated phone systems with a Unix-based server. With a Mac OS X Server Apps Store, there are plenty of companies that would jump at the opportunity to sell ready to go systems that only required plugging in some phone hardware and downloading a server app with a customized Server Admin pane for configuration. It would be easy to deeply integrate office phones with iChat messaging, Bonjour discovery, unified mailbox messaging, and other features that typically cost ridiculous sums from other sources. That application alone would result in thousands of Xserve sales as companies dumped their old PBX systems to go digital with a cost effective, open, and inexpensive system
Specialized Media Servers: Apple bundles its aging QuickTime Streaming Server with Icecast-style MP3 Internet radio streaming, but third parties could provide a variety of alternatives that offered specialized media server features, including a shrink-wrapped solution for serving up HTTP Live Streaming video feeds to iPhone clients. Again, competing server software developers could offer a download package to configure background services that are easy to setup and use in Server Admin. This again would sell many users on the virtue of buying an Xserve as a ready to go solution to media serving needs, from Internet broadcasting to teleconferencing.
Document and media asset management servers: Apple provides basic AFP, SMB, and NFS file serving. Lots of users have special needs for cataloging specialized documents or media assets. Apple’s own Final Cut Server could be sold as a plugin module to Mac OS X Server for central administration. Again, third parties would sell Xserves for Apple as the vehicle for their offerings.
Customer Relationship Management: Companies pay through the nose to set up expensive, complex CRM solutions. With Apple supplying the server hardware and supporting operating system services, CRM vendors could taylor CRM offerings to deeply integrate into companies’ existing resources and provide Apple with the CRM services savvy that it lacks.
Search and Web Services: Apple’s included Wiki collaboration services are easy to use, but there is lots of unaddressed potential in web services that Mac OS X Server could supply if it provided a third party platform for vendors. Google could adapt its own search technology to match its own expertise with Apple’s in hardware. Other wiki providers, other web development tools, and even other blogging and e-procurement software could be wedded to Apple’s server operating system, marrying Apple’s core competency as a platform vendor with the specialized skills of third party developers.
There are too many other specialized server application opportunities to even mention them all. Currently, the market for server software revolves around custom development, resulting in either very expensive solutions or completely free FOSS based solutions that are out of the reach of anyone who lacks development savvy or the resources to acquire it.
Apple advertises Mac OS X Server as “open source made easy.” The next step will be making third party server apps accessible to Apple’s core markets, and alternatively, to spread Apple’s offerings into markets that currently see little relevance in the brand. To do that, Apple needs a build a market and leverage third party expertise.