eduardofv

Artículo sobre OCCMatch en TopManagement

I'm updating our Windows Azure projects to the new version (November 2009 PDC) of the SDK. These are the highlights on the process:

• New namespaces: from Microsoft.ServiceRuntime to Microsoft.WindowsAzure.ServiceRuntime plus the new .StorageClient and .Diagnostics (see below, on logging). Also note that you have to update the References.
• The RoleManager class changed to RoleEnviroment so:
  • RoleManager.GetLocalResource is now RoleEnvironment.GetLocalResource
  • RoleManager.GetConfigurationSe

Yesterday our case study with Microsoft went live here.

It basically explains how we developed our MapReduce implementation on top of Windows Azure to scale the processing of our OCCMatch algorithm. It runs in 200 parallel Azure instances to calculate the best matches for jobs and resumés on OCC, which we send as suggestions via e-mail and are available on My OCC.

I've found that some people are using a technique I haven't seen before (which I've called "twitter traffic hijacking") to divert traffic from a known source to their unknown low-traffic site: post a message with the Twitter @user of the known source and invite to follow you with an attractive message.

In this case, user @unlimitedideas is posting a message: "@OCCMundial Tenemos Vacantes, siguenos !!!" (We have job offers, follow us!!!), referencing us OCCMundial (@OCCMundial on Twitter), which

Eventualmente mensajes así van a ser un problema:

Usar: queretaro -gallos -futbol

(Sí hay un pequeño riesgo de perder noticias importantes de gripe aviar, pero vale la pena por evitar información inútil)