iis - WCF services on Azure -
i planning migrate vps functions azure subscription. have free 3 year bizspark subscription gives me 20 cores, 6 hosted services , 5 storages. believe 2 small instances.
my main aim transfer 10 or wcf applications run on iis7.0 server.
how many wcf services able host azure?
ive been reading , playing azure day, still confused does. current playing, seems each wcf service needs own hosted service, ahve 6 of? or getting confused. wcf services need put in 'hosted service'?
thanks.
let me see if can out bit:
- windows azure platform can deploy applications cloud , not worry building plumbing underlying infrastructure or features such caching, identity management, etc.
- each windows azure subscription has multiple deployment slots, or hosted services. limited 6, meaning can deploy 6 complete deployment packages (with each deployment package consisting of 1 or more virtual machine instances).
- each virtual machine, called role, takes number of cores. small role uses 1 core, medium=2, large=4, , large=8.
- bizspark gives 1500 core-hours monthly. if ran small role instance entire month, you'd consume under 750 hours. thus, can run 2 small role instances 24x7 , still fit within 1500 included core-hours.
- your account capped @ 20 cores, meaning can crank role instances beyond 2. however, if ran 24x7, you'd start incurring costs. if keep monthly consumption under 1500 core-hours, you're fine. so, if ran 20 cores 24 hours, you'd consume 20x24=480 core-hours. @ rate, you'd consume included hours in 3 days.
- each role windows server 2008 r2. web role differes worker role in web role has iis enabled.
- each deployment (e.g. hosted service) may expose 25 externally-facing endpoints (e.g. tcp, http, or https ports). may host wcf service on of exposed ports
- you may host of wcf services in single role, or place them in separate roles. choice, really. it's less expensive host in single role, can have entire service stack running in 2 instances. downside that, if have 1 busy service, , remaining services relatively idle, busy service can starve other services. it's beneficial separate services different roles, , scale accordingly.
- note said can run in 2 instances. if host in 1 instance, incur occasional downtime whenever instance rebooted (e.g. hardware failure, role instance os upgrade, or host os upgrade).
you should download windows azure platform training kit. there, you'll find easy-to-follow labs walk through basics, hosting services, deploying multiple roles, etc.
good luck!
Comments
Post a Comment