30.10.2008, 00:06 | #1 |
Участник
|
Microsoft Dynamics CRM Team Blog: CRM 4: Waiting Workflow VS Windows Service
Источник: http://blogs.msdn.com/crm/archive/20...s-service.aspx
============== Guest blogger Ayaz Ahmad is a CRM MVP who blogs at http://ayazahmad.wordpress.com/. Developing some service or workflow to handle some periodic tasks is a common task when creating a CRM solution. Last week, I was looking for the best way to handle periodic tasks such as sending reminders when creating tasks based on date/time, birthday notification and the like. For example, I have an entity project schedule with thousands of records of this entity. For each of these I want to send email reminders. For each record I can have a waiting workflow which results in thousands of waiting workflows. Or, I can develop a Windows service that runs overnight and process records according to my criteria which includes sending reminders. What about performance considerations for hundreds of waiting workflows versus one windows service instance running overnight? Here are some merits and demerits for both techniques: 1. Workflows are configurable with no code but we would need to create a configuration mechanism for Windows service and scheduled tasks.Although waiting workflows will not consume any CPU or memory resources, the overhead of handling change and strain on system during peak hours make them less favorable when compared to using a Windows service. Personally I feel the control and maintainability of a Windows service is better than workflows, especially when you take all of this into consideration. Cheers, Ayaz Ahmad Источник: http://blogs.msdn.com/crm/archive/20...s-service.aspx
__________________
Расскажите о новых и интересных блогах по Microsoft Dynamics, напишите личное сообщение администратору. |
|
|
Опции темы | Поиск в этой теме |
Опции просмотра | |
|