Skip to content
This repository was archived by the owner on Sep 12, 2018. It is now read-only.
This repository was archived by the owner on Sep 12, 2018. It is now read-only.

Support nanomsg transport #36

Open
@bitmage

Description

@bitmage

Problem: I don't want to setup/maintain a kafka cluster.

Solution: I'm writing in support for nanomsg in a fork:

https://github.com/bitmage/zdb

Still in the middle of writing the nanomsg implementation, but you can see how I've moved Kafka into it's own plugin under src/transport.

This is kind of a significant refactor, and I was just wondering what the level of desire would be to merge such changes back in? I'd be willing to work to make that happen, but if there's no desire to merge then I could simplify the design by removing layers of queueing/threading that are redundant with nanomsg.

Just want to feel out the current maintainers' thoughts on whether this transport abstraction would be of value to the project.

Thanks.

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions