Structuring Azure solution with multiple roles -
i'm curious how others have structured (or suggest structuring) azure applications have multiple roles. in particular i'm curious how have them broken our between subscriptions , hosted services.
in particular case have web role hosting webapp & api. changes quickly, multiple times per day. have several different worker roles things video processing, email sending, , reporting/analytics. workers change rarely, less once month. have running in single subscription. each role in own hosted service.
this setup lets deploy 1 role without affecting others. avoids interrupting worker roles unnecessarily, since in middle of long (10+ minute) processing jobs have restarted.
so how guys it?
part of reason ask microsoft seems want put single hosted service. eg, new caching function that's in preview visible within single hosted service, makes useless layout have.
this bit of opinion, think have right of it. there advantages deploying single package roles (atomic updates, versioning, etc.). however, in more complicated scenarios, have found splitting different deployments , hosted services works well. if want geo-redundancy, have have different deployments anyway.
if careful versioning (assuming deployments communicate), can have different deployments , benefit of quicker deployments. found our worker roles have higher deployment ratio our web roles, makes sense split web roles out. new windows azure websites feature, looking @ splitting them out more , running web portion of our app that. our api go there or deploy other dedicated instances.
the thing have not done split between subscriptions. don't think there technical reason this. there might business 1 around quotas, reality subscription not matter much. can real pain later if use mgmt api use different subscription ids different hosted services. hesitate mix , match storage , hosted services different subscriptions management purposes. probaby idea keep in same sub.
Comments
Post a Comment