RVS_ParseXMLDuration VS laminarmq

Well, these ones aren't "half-baked," but they are no longer being maintained (archived):

[0] https://github.com/RiftValleySoftware/RVS_IPAddress

[1] https://github.com/RiftValleySoftware/RVS_ParseXMLDuration

[2] https://github.com/RiftValleySoftware/RVS_ONVIF

This project is unfinished (I just walked away from it, as it wasn't really giving me what I wanted):

[3] https://github.com/RiftValleySoftware/RVS_GTDriver

This one is "half-baked," I believe. I never really took it particularly far:

[4] https://github.com/RiftValleySoftware/RVS_MediaServer

Not completely. The way that it works for me, is that I start work on a project, and, while building, I notice that some code that I'm working on is:

1) Pretty complex, and fairly insular; and/or

2) Possibly useful, elsewhere.

If that's the case, I will then stop work on the main project, and take some time to extract and "genericize" the subproject. I'll usually set it up as a standalone open-source project; complete with tests and documentation.

This may happen before I have completed the coding in the main project, or may happen as the result of a review, after the fact.

In some cases, I very clearly need to develop a subproject before starting on the main project, or before certain milestones within that project (for example, SDKs or drivers). In that case, the timelines are completely separate.

If you look at my GH repos, you'll see a whole bunch of these projects, including some rather strange ones, like an XML duration parser[0]. These are the types of projects that I extract.

In some cases, I end up not using the extracted project in my main project (happens to some of my UI widgets). In that case, even though I am not using it, I still have an excellent project for the future. Here's an example[1]. I have ended up not using the spinner in my own work, as it was too obtrusive a widget, but it's nice to have it available for future projects.

[0] https://github.com/RiftValleySoftware/RVS_ParseXMLDuration

[1] https://github.com/RiftValleySoftware/RVS_Spinner

laminarmq: https://github.com/arindas/laminarmq

I am building a message queue from scratch in Rust. It is intended to be a resource efficient alternative to Apache Kafka. (It does not rely on any Kafka libraries.)

It has similar concepts like topics and partitions. It is intended to be distributed in nature, with no reliance on any third party component.

Currently it only provides a segmented log implementation which can be used on it's own if necessary. We support both persistent and in-memory storage.

It is still very much in a nascent stage as there are no message queue level APIs or Web endpoints yet.

I tried to keep it as decoupled from different Rust async runtimes as possible to make it easier to integrate to different ecosystems. It currently supports tokio and glommio.

There is also an example to show how the segmented log might be used in a server:

https://github.com/arindas/laminarmq/tree/examples/laminarmq...

Next steps would be to design the message queue level APIs and gradually implement the distributed components.

This is the first time I am implementing something at this scale so any feedback or advice would be great.