Why Write a .NET API For RabbitMQ?

2 Kicks

submitted by rcash(4149) 8 months, 12 days ago

Here is an interesting article discussing messaging protocols and how one developer is using the MVC to create a newer and more powerful API. One question I’ve been asked quite a lot, is ‘why?’. Why am I building a .NET API when one is already available; the C# AMQP client from RabbitHQ? Think of AMQP as the HTTP of messaging. It’s a relatively low-level protocol. You typically wouldn’t build a web application directly against a low-level HTTP API such as System.Net.WebRequest, instead you would use a higher level toolkit such as WCF or ASP.NET MVC. Think of EasyNetQ as the ASP.NET MVC of AMQP.

add a comment |category: DirectoryServices |Views: 10
Tweet