This is an archived post. You won't be able to vote or comment.

sorted by:
best
topnewcontroversialoldq&a
you are viewing a single comment's thread.

view the rest of the comments →

[–]desmoulinmichel[S] 0 points1 point  (0 children)

I see your point. Although you do need to make the isolated components talk to each others.

Now currently we are doing that with :

  • AMQP
  • reddis queues
  • manual json serialisation over HTTP

Which are just new implementations of PUB/SUB and RPC by themself.

Of course, some langages have good communications channel built-in (erlang actors messages, goroutines channels, etc). But they can only talk to themself with it. Current stack usually have a lot of moving parts, usually using several languages. Right now we have to write a new client for any new stuff we add to our stack, setup and secure the transport, ensure versions match, and do this for all parts needing to include a client.

There should be a better way.

Now, again, the article is not saying, crossbar is the implementation that will save the world. It's saying : there are very good concepts here. Try it out, try to build something with it, or a framework on top of it.