Now that I'm learning more about Mesh, I'm surprised at what a big undertaking it is. For example, this recent post on the Live Mesh blog talks about how they run the cloud services, which offers some interesting insights into how Mesh's "services" part of their "Software + Services" works.
In Mesh, writes Alex Mallet, a dev lead on the Live Mesh team, cloud services can be grouped into four areas:
- Feed & Data Sync
- Authentication & Authorization
- Maintaining & Fanning out the Transient State
- Connectivity Services for Sync and Remote Desktop Access
Mesh's front-end services are accessible only via HTTPS. Back-end services use HTTPS and custom protocols layered on TCP. Most services are written in C# and all services sit on top of a common runtime library.
What's really interesting though (and funny!) is when Mallet describes building the full-scale datacenter deployment and management system: he says they "chose the lazy smart route" to do so. The Mesh team used the the Autopilot framework, which is currently used by the Windows Live Search team to manage tens of thousands of datacenter machines. Mesh isn't there yet, but hopes to be!
If learning more about the services part of Mesh is the sort of thing that interests you, go ask your question in the comments section of his post.