Oracle Beehive

» see oracle.com/beehive as it lived, on the wayback machine

~ the eulogy ~

Oracle Beehive was announced at Oracle OpenWorld in September '08 as the successor to Oracle Collaboration Suite. the pitch was a single java-stack enterprise platform that combined email, calendar, instant messaging, team workspaces, document libraries, conferencing, voicemail under one administrative roof. version 1.5 followed in May 2009 with web-based workspaces. version 2.0 came in February 2010.

the product targeted oracle's existing enterprise customer base, the kind of shop that was already running oracle database licenses and wanted one vendor for the whole stack including the inbox. it competed with microsoft exchange on the enterprise side, with google apps for business on the cloud side. ibm lotus notes was the legacy incumbent it expected to displace.

by 2014 the world had moved. google docs and microsoft 365 had effectively settled the cloud-collaboration market and oracle had launched documents cloud service as its replacement strategy. beehive's voicemail tier formally lost premier support in february 2015 and the main product disappeared from oracle's standalone catalog in the same window. the beehive name was retired without a discrete shutdown announcement, which is its own genre of corporate death.

~ the dossier ~

~ what it actually was ~

the engineering pitch for beehive was protocol completeness. IMAP, SMTP, CalDAV, XMPP, WebDAV, LDAP, all of the open standards your old gear could speak. inside the company, that meant outlook clients could connect like exchange. thunderbird could connect over IMAP. mobile clients could sync calendars over caldav. on paper that solved the heterogeneous-enterprise problem better than exchange, which was the whole microsoft moat.

in practice the deployment story was complicated. running beehive meant running oracle database, weblogic application server, http server, identity manager. the moving-parts list was enterprise-java sized. by 2010 the buyers who would have signed a beehive contract were the same buyers who had started piloting google apps for domains and realizing the email server was no longer something they wanted to operate themselves.

~ how it ended ~

the death was not a single event. oracle did not ship a final-of-line bulletin. premier support for the voicemail component ended in early 2015. the documents cloud rebrand absorbed the document-library functionality. the email side was quietly migrated to oracle's hosted offerings or to whatever the customer was moving to next. by 2016 beehive was no longer a name in oracle's middleware portfolio.

i did not touch this product. enterprise oracle was not the part of the stack i worked on at any point. but every cs engineer who joined a turkish bank or telco in the 2010-2015 window came back with a story about being on the side of an oracle migration project. beehive was one of those names that showed up in those projects, on the side that was being replaced rather than the side that was winning.

@}-->--

              )
             (_)
            .-'-.
            |   |
            |   |
            |   |
            |   |
          __|   |__   .-.
       .-'  |   |  `-:   :
      :     `---'     :-'
       `-._       _.-'
           '""""""

« previous  ·  random  ·  next »