CODEWITHSUNDEEP
websocketautobahnwamp-protocolcrossbar
Hedge
Hedge

Reputation: 16768

Downsides of using Autobahn as WAMP router?

I'm currently looking into using the WAMP-protocol to synchronise between server and clients of my future web-applications.

They recommend using crossbar.io as the router but since Autobahn supports all four roles (publisher, subscriber, caller, callee) itself I'm wondering why I would need another router framework like crossbar.io at all?

I'd like to use node.js with Autobahn|JS as the router and Autobahn|JS in the web-browser as the client. Is this feasible or am I missing something here?

Upvotes: 0

Views: 1585

Answers (1)

gzost
gzost

Reputation: 2445

Autobahn(JS/Python/CPP) supports all four client roles, but since WAMP is a routed protocol, you still need a WAMP router. Autobahn does not provide that, and there's now way in which you could use AutobahnJS to create a WAMP router on Node.js.

The WAMP router is not a framework - it's a component which you configure (authentication, authorization, transports etc.) and then just leave running. When everything is configured properly, this is completely transparent for your application.

I'm part of the Autobahn and Crossbar.io projects - so my recommendation is Crossbar.io, but there are other WAMP routers out there. These differ e.g. in regards to the amount of features they implement and their performance. As long as you don't rely on the features of a particular router, you can swap out the WAMP router at any time.

Upvotes: 3

Related Questions