parity3

The await here could serve the purpose of providing backpressure, which would be needed when the number of pending logs is growing faster than the ability to write them out,...

Happy to lurk on over here. Re: the code review, I don't have enough time to really dig in so all I can do is yap away on my opinions...

Wow, some of these, particularly the stream sorting may do well as their own separate repos/libraries! Another possible example is to implement one of the function-as-a-service protocols with some tuning...

Another piece of code that may be nice to see is for a tractor controller app to run as a daemon that some other sync or polyglot app could call...

I don't have any opinions on this but thought I'd add a couple recent references to software licensing I've come across: [sentry blog post](https://blog.sentry.io/2019/11/06/relicensing-sentry) [changelog podcast interview episode talking about...

Regarding this BSL-rollover trend (mentioned in my sentry comment above) (ie firmly in the more-complex direction, but honestly not OSS purely out of technicality), [cockroachdb](https://www.cockroachlabs.com/blog/oss-relicensing-cockroachdb/) has a blog post summarizing...

Have you considered switching from the generator paradigm to the synchronous coroutine paradigm? The outer layer would be simpler and not require as many queues (at the expense of the...

Not sure if this helps anything or not, but I remember seeing this project a while back: https://github.com/KholdStare/generators-to-coroutines It actually provides a decorator which takes any iterator function and ast-transforms...

If you could tuck the CBS concept into a plugin or middleware-style module and have an alternative or bare-implementation which allows everything to be called by everyone, that would be...

I'm impartial to whether CBS is the default, but I do recognize that is the way the industry/community leans. I just think sometimes putting security first tends to tax both...