开云体育

Wallaroo connector

[email protected] All Messages By This Member #138 Hi Just wanting to ask, what is the benefit of writing connector in pony rather than python ? So I manage writing connector for nats server (after digging through the source code), then I found that the connector is a separate process, if it is in pony, it will be in one process right ? The second, the connector api is marked experimental, any plan on breaking change ?
Sean Allen #139 Hi. Answers inline below. On Fri, Jan 25, 2019 at 8:37 AM <nuhamind2@...> wrote: Hi Just wanting to ask, what is the benefit of writing connector in pony rather than python ? So I manage writing connector for nats server (after digging through the source code), then I found that the connector is a separate process, if it is in pony, it will be in one process right ? Connectors are all external processes. You could write a NATs source in Pony that runs directly in the Wallaroo binary. For that, you'd need to write Pony code that gets compiled directly into Wallaroo. You'd probably also have to change the initialization process and a variety of other things. In the end, not something most people are probably going to want to do.? Connectors are separate processes which allows the writer to only worry about the connector, not any Wallaroo plumbing. ? The second, the connector api is marked experimental, any plan on breaking change ? _._,_. It's possible based on feedback and usage that we will end up making breaking changes. There are planned changes around resilience, replayability, and more thoroughly building those into the protocol.
[email protected] All Messages By This Member #140 Thanks for the prompt reply Why not default to pickling for connector encode/decode ? as communication between worker already default to pickling.
Sean T. Allen #141 The connector protocol is language agnostic. You can write a connector in any language you want, not just Python. For a specific connector, you could pickle the data and send it across as long as you knew that the receiver can deserialize it. The idea that the Python library support for connectors should default to pickling for serialization is an interesting one, in the context of the Python library support. Seems like a good issue for the Github issue tracker where it could be discussed more fully. toggle quoted message Show quoted text On Fri, Jan 25, 2019 at 5:37 PM <nuhamind2@...> wrote: Thanks for the prompt reply Why not default to pickling for connector encode/decode ? as communication between worker already default to pickling.

Previous Topic Next Topic