The Zen of Hosting: Part 2 - 40000 Foot View

So part 1 was the reasoning and the bulk of the non-technical in the series, this post is about the high level view of the architecture. At it's core a hosted network is just a normal network except that it needs to not only service one organisation but multiple organisations. The biggest problem with this is that most networking technologies aren't designed for handling multiple organisations and a core strategy for VirtualBox was to use Microsoft technologies (we are a Microsoft Gold Partner and that’s where are strongest skills are as an organisation). So lets look at what that could mean:
  • User Management: Active Directory
  • Email: Microsoft Exchange Server 2007
  • Portal/Intranet: Microsoft Office SharePoint Server
  • CRM: Microsoft Dynamics CRM
  • Database: Microsoft SQL Server
  • ERP: Microsoft Dynamics GP

This shouldn’t be a shocker of a list, in fact it’s kind of the standard shopping list for any Microsoft based solution but the problem is that some of these products don't easily allow multiple organisations to use them. So lets just start with the most commonly used item on that list: Active Directory, which in my view is also the like the least able to cope with multiple organisations.

Based on what I have seen most large companies, which have a need for multiple organisations in a single deployment, seem to set up a forest and trusts and connect multiple domains together in the forest. This lets each domain be individually named and managed and provides the security for central administration and prevents each domain from doing anything to other domains. The problem with this is that it is multiple domains, which means that the administration overhead is very high, I think I would need a server at least per domain, and I really only want one because I don’t want to deploy everything multiple times. Each service should be deployed once and used many.

Well Microsoft has actually solved this with an interesting solution named Hosted Messaging and Collaboration (HMC), which is currently in version 4.0. HMC is developed by the same division as developed one of my other favourite technologies, Customer Care Framework (CCF). HMC shares the same thought leading as CCF.  What I mean by this is they are are taking very new or different ideas and providing a solution to deliver them. The solution for HMC is delivered in the same way as CCF, in that it is a guidance package.

Next time I will jump into what is HMC and then after that we’ll get back to how HMC allows us to to take one AD domain and put multiple companies into it.


 

[...] how does that help with running lots of systems and doesn't HMC break on Win2k8 (see way back to part 2)? Well Win2k8 has the best virtualisation technology Microsoft has ever developed, named Hyper-V. [...]

[...] In part 2 I wrote about this technology called Hosted Messaging and Collaboration (HMC) and that it is [...]

[...] In part 2 I started to write about Active Directory and how to get a single domain to work with multiple [...]

Comment viewing options

Select your preferred way to display the comments and click "Save settings" to activate your changes.

Post new comment

The content of this field is kept private and will not be shown publicly. If you have a Gravatar account associated with the e-mail address you provide, it will be used to display your avatar.
  • Web page addresses and e-mail addresses turn into links automatically.
  • Allowed HTML tags: <em> <strong> <cite> <code> <ul> <ol> <li> <dl> <dt> <dd>
  • Lines and paragraphs break automatically.
  • Syntax highlight code surrounded by the <pre class="brush: lang">...</pre> tags, where lang is one of the following language brushes: as3, applescript, bash, csharp, coldfusion, cpp, css, delphi, diff, erlang, groovy, jscript, java, javafx, perl, php, plain, powershell, python, ruby, sass, scala, sql, vb, xml.

More information about formatting options