Modularity like this is a huge plus for production deployments - it gives the ability to scale more effectively and maintain a closer match between resources and services where appropriate.
I think it's a solid idea. We're almost certainly going to want to end up with this level of control so it makes sense to ensure the framework is in place from the get go. That will result in fewer potential design dead ends as well as cleaner upgrades in the future because we'll have that many fewer significant paradigm shifts. On Wed, Apr 21, 2021 at 6:24 AM Enrico Olivelli <[email protected]> wrote: > Hello, > Pulsar 2.8.0 is coming near to the release and we want transactions to > be "production ready". > > If I understand correctly now we start the Transaction Coordinator > service inside the Broker. > > Does it make sense to have the option to run the TC as a separate > service, as we do for the Functions Worker ? > > For instance in a big cluster, with many brokers, an user may like to > dedicate machines to the role of Transaction Coordinator and do not > serve all of the usual Broker activities. > > The same problem will also go into the Helm Chart, it would be better > to have the ability to configure the transaction related services with > specific options. > > What do you think ? > > > Enrico > -- Chris Herzog Messaging Team | O 630 300 7718 | M 815 263 3764 | www.tibco.com <http://www.tibco.com/>
