Mimecast and file server destruction
Online mail services lead to filer destruction - maybe
Analysis Mimecast is a UK-based supplier of unified email management services. Around the end of 2002 it started to build an appliance function that would unify the many daisy-chained email functions, (anti-spam, anti-virus, data leak prevention, signaturing) that were all implemented as separate boxes through which emails had to flow before ending up in peoples' inboxes. How it has done this and what it means leads logically through cloud file storage (CFS) to a deadly problem for filer suppliers.
The key thing chief technologist and co-founder, Neil Murray, decided was to put the actual storage in the cloud. Instead of using a client-side appliance or replicating customers' own email serving and storage functions in a Mimecast data centre, Murray decided to use a Google-like grid set-up. It uses Linux commodity servers, commodity filers, and Mimecast-developed software, with open source components, to provide an email repository that could scale massively and answer requests - where is Joe.Manager's subject X e-mail? - very, very quickly by parallelising the search across many gridded servers.
The result is a core platform with email-aware functions layered on top, which has proved attractive to many customers in the UK and abroad. Murray likens it to SAP, another core platform with business modules layered on it or plugged in, and says Mimecast will add file archiving this year. It will also add SharePoint support at some stage. Then Mimecast will have a single, multi-tenant-aware repository, that single instances file-level content and provides search, backup, restoration, archiving, compliance and general document management services in the cloud across the email, file and SharePoint domains.
Step back and consider Mimosa, which recently added the storage and archiving of SharePoint content onto its NearPoint archiving platform. This already covers Exchange email and unstructured Windows file archiving, with search, eDiscovery and compliance capabilities. It's another core platform with content-aware plug-ins providing for the capture of several data types and their storage in a central repository, followed by the provision of end user functions for search, eDiscovery, compliance, retention policies and so forth. Mimosa and Mimecast are parallel tracking in this super content management space, except that Mimecast is building its own system infrastructure in the cloud.
Many suppliers are inching towards this consolidated content management idea and are coming up with different application directions:
- Traditional backup such as EMC, Symantec, IBM Tivoli, HP and Backbone are all about capturing and storing data. Several are adding cloud backup services such as Mozy and Norton Online Backup
- Online backup - Mozy, Nirvanix, Carbonite, Spare Backup and others are offering cloud backup
- Enterprise Content Management - Documentum and others offer ECM and are extending its functionality to widen the content types supported
- Search - Autonomy, Reccomind and others are offering search, eDiscovery and other capabilities in document data repositories
- Email archiving - Mimecast, Mimosa, Waterford Technology and others are building searchable mail repositories and adding additional content type support
- Records management - Iron Mountain and other document records vaulting service suppliers are moving into digital records vaulting.
Looking across these six categories we can view them as converging into a single product/service category, which is a multi-type service including content capture, storage, hygienic cleansing, access, continuity, search, eDiscovery, retention and compliance - a super content management system that will gradually be developed over the next five to ten years.
According to Mimecast's Murray, it is easier, (meaning more cost-effective,) and simpler to write the code for this from scratch and do it on a Google grid-like system infrastructure. It is better, he says, to do it this way and grow a core infrastructure that can scale, rather than buy in technology and cobble it together with existing products to provide the comprehensive functionality required. It is also better to do this on a massively scalable grid server base because that is far more cost-effective than using existing server-file storage array combinations.
Only by parallelising functions across such a grid can you get the responsiveness needed and on a cost-effective scale without the expensive over-provisioning you would be forced to use with conventional server-filer technology to meet the same goals.
Mimecast's grid infrastructure application has much Java code, a grid-based relational database service, and the open source Lucene full text indexing application with added grid awareness. The Linux x86 commodity servers running this code are linked across gigabit Ethernet with SATA drive arrays storing the data.
Murray is convinced that this Mimecast-developed, Google-like infrastructure is far more cost-effective than any cobbled-together set of applications running on conventional server-filer infrastructure. By providing its software-as-a-service, Mimecast can spread its costs across many customers. By writing its own software, profit margins are enhanced.
Sponsored: Optimizing the hybrid cloud