Hi,
Crossbar.io _already_ is able to scale-up and scale-out application
components (container/guest workers). It fully supports shared
registrations. There is no LB involved, as Crossbar.io itself is acting
as the LB rgd the WAMP traffic routed to app components.
Crossbar.io (trunk) is also already able to scale-up Web services.
What's missing is scale-out for Web services, and both scale-up and
scale-out of actual WAMP routing (router workers).
When we have that, you will need a L4 LB in front of the Crossbar.io
nodes to (randomly) distribute incoming connection at the TCP level to
backend nodes.
Cheers,
/Tobias
Am 20.11.2015 um 15:30 schrieb Iulian Nitescu:
> Hi Alex,
>
> Aha, right. So you are saying there is a way to configure workers into
> clusters behind a load balancer. Do these workers need a special
> configuration? For example is this bit of the documentation correct
> (
http://crossbar.io/docs/Shared-Registrations/)?. Is there even need for
> a load balancer in that case?
>
> If I understand you correctly, it won't work if I put 2 router behind an
> LB?
>
> Thanks,
> Iulian
>
> On Friday, November 20, 2015 at 3:19:59 PM UTC+1, Alexander Gödde wrote:
>
> Hi Iulian!
>
> Scalability features are under construction. There aren't yet any
> router-to-router features. This means that load balancing of workers
> is restricted to workers connecting to a single router. We're
> working on going beyond this, but unfortunately can't give a
> timeframe for this.
>
> Regards,
>
> Alex
>
> Am Freitag, 20. November 2015 12:59:45 UTC+1 schrieb Iulian Nitescu:
>
> Hi,
>
> We are looking to build parts of our system with
crossbar.io
> <
http://crossbar.io> (mainly Python). We have played around with
> some examples and it looks great, so first I have to
> congratulate everyone working on
crossbar.io
> <
http://crossbar.io> - excellent initiative. My questions are
> <
https://groups.google.com/forum/#!msg/autobahnws/RbYylAj_SZ4/Cq4bdC2s6VMJ>.
>
> What is the current state of the scalability features now? As
> the OP in the mentioned thread, we also need to be able to scale
> - basically worker + router load balancing (==> workers
> registering the same procedures). The scenario is to use Amazon
> Container Services and deploy Docker tasks with the
crossbar.io
> <
http://crossbar.io> stack on them.
>
> Is the feature set complete enough to allow running multiple
> workers and routers behind ELB?
> Is it possible to cluster workers (on separate instances) such
> that only one of them receives receives the message?
>
> At the beginning of the project it is no problem if we have to
> use the trunk from git. There is also no problem with us
> managing and configuring the Docker containers, ELB etc.
>
> Thanks,
> Iulian
>
> --
> You received this message because you are subscribed to the Google
> Groups "Crossbar" group.
> To unsubscribe from this group and stop receiving emails from it, send
> an email to
crossbario+...@googlegroups.com
> <mailto:
crossbario+...@googlegroups.com>.
> To post to this group, send email to
cross...@googlegroups.com
> <mailto:
cross...@googlegroups.com>.
> To view this discussion on the web visit
>
https://groups.google.com/d/msgid/crossbario/a0f3276c-2f75-4ec9-838f-63dee0060572%40googlegroups.com
> <
https://groups.google.com/d/msgid/crossbario/a0f3276c-2f75-4ec9-838f-63dee0060572%40googlegroups.com?utm_medium=email&utm_source=footer>.
> For more options, visit
https://groups.google.com/d/optout.