Skip to main content

Auto-start la servicii WCF hostate pe IIS

Sunt cazuri când avem servicii WCF pe IIS care necesita un timp lung pentru iniţializare. Din aceasta cauza primul apel a unui serviciu poate sa dureze o veşnicie.

La încărcarea aplicaţiei, IIS ne ajuta destul de mult: iniţializează AppDomain, compilează dacă este nevoie codul( în principiu pregăteşte aplicaţia). Aproape totul este pregătit, mai puţin iniţializarea serviciilor, care este lăsata în seama noastră.

Pentru aceasta problema exista mai multe soluţii:

  • La iniţializarea aplicaţiei se pot încarcă resursele necesare serviciului static sau într-un IoC.
  • Apelul "virtual" a tuturor serviciilor, în momentul în care serverul porneşte. Prin aceasta metoda toate resursele folosite de către servicii o sa fie deja încărcare.
  • Implementarea unui mecanism de auto-start la servicii.

O sa descriu mai amănunţit ultima soluţie propusa. .NET împreuna cu IIS 7.5 ne pune la îndemâna un mecanism destul de simplu prin intermediul căruia putem sa iniţializam automat un serviciu şi sa controlam obiectele care sa se iniţializează în acel moment.

Primul pas este sa selectam în IIS aplicaţia care conţine serviciile şi sa selectam Manage WCF andWF Services. Aici trebuie sa activam Auto-Start. In acest moment toate serviciile o sa fie pornite automat.

Următorul pas este sa găsim o modalitate prin care putem sa controlam modul în care fiecare serviciu este iniţializat. Pentru acest lucru este nevoie sa cream un service host factory personalizat. Pentru acest lucru este nevoie sa cream o clasa ce moşteneşte ServiceHostFactoryBase. Prin intermediul metodei CreateServiceHost putem sa executam orice cod care dorim sa fie rulat la iniţializarea serviciului, trebuie doar sa avem grija sa returnam instanta a unui ServiceHost.

public class ValidateServiceHostFactory : ServiceHostFactoryBase
{
public override ServiceHostBase CreateServiceHost(string constructorString, Uri[] baseAddresses)
{
//Custom code folosit pentru incarcarea anumitor servicii;
InitValidateService(baseAddresses);
return new ServiceHost(typeof (ValidateService), baseAddresses);
}
}
Tot ce ne-a mai rămas de făcut este în .SVC sa adaugăm la atributul Factory cu locatia ServiceHostFactory pe care noi l-am implementat:

<%@ ServiceHost Language="C#" Debug="true" Service="Services.ValidateService" CodeBehind="ValidateService.svc.cs" Factory="Services.Factory.ValidateServiceHostFactory " %>
Gata, avem un serviciu care porneşte automat la iniţializarea aplicaţiei în IIS, la care putem sa controlam ce resurse sa se iniţializeze prin factory.

Comments

Popular posts from this blog

Why Database Modernization Matters for AI

  When companies transition to the cloud, they typically begin with applications and virtual machines, which is often the easier part of the process. The actual complexity arises later when databases are moved. To save time and effort, cloud adoption is more of a cloud migration in an IaaS manner, fulfilling current, but not future needs. Even organisations that are already in the cloud find that their databases, although “migrated,” are not genuinely modernised. This disparity becomes particularly evident when they begin to explore AI technologies. Understanding Modernisation Beyond Migration Database modernisation is distinct from merely relocating an outdated database to Azure. It's about making your data layer ready for future needs, like automation, real-time analytics, and AI capabilities. AI needs high throughput, which can be achieved using native DB cloud capabilities. When your database runs in a traditional setup (even hosted in the cloud), in that case, you will enc...

Cloud Myths: Migrating to the cloud is quick and easy (Pill 2 of 5 / Cloud Pills)

The idea that migration to the cloud is simple, straightforward and rapid is a wrong assumption. It’s a common misconception of business stakeholders that generates delays, budget overruns and technical dept. A migration requires laborious planning, technical expertise and a rigorous process.  Migrations, especially cloud migrations, are not one-size-fits-all journeys. One of the most critical steps is under evaluation, under budget and under consideration. The evaluation phase, where existing infrastructure, applications, database, network and the end-to-end estate are evaluated and mapped to a cloud strategy, is crucial to ensure the success of cloud migration. Additional factors such as security, compliance, and system dependencies increase the complexity of cloud migration.  A misconception regarding lift-and-shits is that they are fast and cheap. Moving applications to the cloud without changes does not provide the capability to optimise costs and performance, leading to ...

Cloud Myths: Cloud is Cheaper (Pill 1 of 5 / Cloud Pills)

Cloud Myths: Cloud is Cheaper (Pill 1 of 5 / Cloud Pills) The idea that moving to the cloud reduces the costs is a common misconception. The cloud infrastructure provides flexibility, scalability, and better CAPEX, but it does not guarantee lower costs without proper optimisation and management of the cloud services and infrastructure. Idle and unused resources, overprovisioning, oversize databases, and unnecessary data transfer can increase running costs. The regional pricing mode, multi-cloud complexity, and cost variety add extra complexity to the cost function. Cloud adoption without a cost governance strategy can result in unexpected expenses. Improper usage, combined with a pay-as-you-go model, can result in a nightmare for business stakeholders who cannot track and manage the monthly costs. Cloud-native services such as AI services, managed databases, and analytics platforms are powerful, provide out-of-the-shelve capabilities, and increase business agility and innovation. H...