apparatus / mu

A message based router for building distributed systems
MIT License
26 stars 1 forks source link

mu v seneca transport #70

Closed tomdavidson closed 7 years ago

tomdavidson commented 7 years ago

Im new to the scene and trying to understand. Can someone compare and contrast mv and senecajs transport?

pelger commented 7 years ago

Hey @tomdavidson, they are very similar in intent. The aim of Mu is to implement two of the key ideas in seneca namely - 1). pattern matching / pattern language and 2). transport independence. The idea is to provide a simple lightweight module that doesn't have the rest of the overhead that comes with the seneca framework. In short if you want to use a full framework then go with seneca, if you prefer something that is more cut down then go with Mu - hope that helps?

tomdavidson commented 7 years ago

Perfect explanation and just want I needed. Thank you.

pelger commented 7 years ago

Welcome :)

tomdavidson commented 7 years ago

Adding on to this closed issue for other inquirers. At this time Mu does not have its own distributed messaging such as Seneca Mesh.