NAME
Beekeeper::Service::Router::Worker - Route messages between backend and frontend buses
VERSION
Version 0.03
SYNOPSIS
DESCRIPTION
Router workers pull requests from all frontend brokers and forward them to the single backend broker it is connected to, and pull generated responses from the backend and forward them to the aproppiate frontend broker which the client is connected to.
Additionally, routers include some primitives that can be used to implement session management and push notifications. In order to push unicasted notifications, routers will keep an in-memory shared table of client connections and server side assigned addresses.
If the application does not bind client sessions the routers can scale really well, as you can have a lot of them in a large number of servers.
But please note that when the application does use the session binding mechanism all routers will need the in-memory shared table, and this shared table will not scale as well as the rest of the system. So a better strategy (some kind of partition) will be needed for applications with a large number of concurrent clients.
TODO
Measure and report the percentage of busy time ('load' in bkpr-top). This metric is essential to assess the routing capacity of a given system.
SEE ALSO
AUTHOR
José Micó, jose.mico@gmail.com
COPYRIGHT AND LICENSE
Copyright 2015-2021 José Micó.
This is free software; you can redistribute it and/or modify it under the same terms as the Perl 5 programming language itself.
This software is distributed in the hope that it will be useful, but it is provided “as is” and without any express or implied warranties. For details, see the full text of the license in the file LICENSE.