Queue choice


hi,

i looking queue management system/frameworks , coding on .net platform.

i describe basic expectation:

e.g. if user submits data stored in queue if machine on queue hosted if goes down should have failover mechanism. data in queue analysed other component , removed queue.

i reading queues in next couple of weeks , know 1 famous.

few people suggested kafka,rabbitmq, activeque etc. job go through few systems , select 1 fits

my requirement know one's not suitable .net.

please guide me through links or articles me make choice.

regards,

abhagwat

if went appfabric have 2 servers taking input queue , sending  them on whatever want.

windows workflow can sorts of stuff , store data in message queues.

i'm not sure happens if 1 machine goes bang since can share across several it's more resilient 1 machine , scales well.

otherwise.

once message arrives in queue can stored disk.

you put on nas hot replaceable drives.

run machine on virtual machine , have standby physical server restore in event of catastrophic failure.

disks failure point in server.


hope helps.
recent technet articles: property list editing;   dynamic xaml



Visual Studio Languages  ,  .NET Framework  >  Visual C#



Comments

Popular posts from this blog

Azure DocumentDB Owner resource does not exist

BizTalk Server 2013 Azure VM Log Shipping and HA for hosts

How to Share webservice object to all user