bkiran

Appreciate the feedback. Will edit the post and check for other grammar errors

Agreed, reproducibility is a huge benefit. Being able to spin up a new machine quickly with a config you already know works is an awesome feeling.

I could never get around on longhorn or any of the other "lightweight" K8 distros. I guess that's why I spent time setting up NixOS and writing this post.

Okay nice, seems like various storage services for a home lab setup. Seems like a cool project. Especially if you can distribute it across all those NAS's

This hits the nail on the head. Well said.

I really like being able to manage the managing and host machine in one configuration. It's a blessing from an Op's perspective.

Troubleshooting Nix is mind-numbing. For some of the benefits, it's the price that is need to be paid

Thanks for the perspective. I mainly use NixOS to run my server's not personal machines. I can see why it can be a frustrating experience for a machine that you just want to run personal stuff on.

In my instance of creating server machines(cattle), the configurations are pretty light and what's important is the reproducibility aspect of it. If I need to take one down and rebuild another it takes about 10 minutes. All the upfront work of configuring Nix for that one machine has paid off.

Yeah I agree it's manual but it takes about 5 minutes to SCP the password onto the machine.

I have some playbooks I setup to creating a new machine. All in all it takes about 10 min to get it up and running. Maybe not instant but at the moment I don't need anything else.

Nice, would love to know how it goes. What kind of storage and DB's are you planning to work with?

To each their own. When K8's is managed it's awesome.

I would like to do without the headache of dealing with K8's installation or some orchestrator layer. I can "schedule" my on application instances at the size I'm working with.

Also, I run this setup on cloud vm(multiple actually). So it's not restricted to running on a single machine running in a closet.

I'm using Cap'N Proto in a message broker application(LcuidMQ) I'm building for serialization. It has allowed me to created client applications rather quickly. There are some quirks can be difficult to wrap your head around, but once you understand it is really solid.

There are some difference between the language libraries and documentation can be lacking around those language specific solutions. I'm hoping to add blog articles and or contribute back to the example of these repositories to help future users who want to dabble.

Check out my repo here for how I use it across Rust and Python, with Golang coming soon: https://github.com/lucidmq/lucidmq

I've been working on something that may fit your criteria. The API is kafka-like and it's whole goal is to provide an easy to use local-first stream datastore/data-engine.

It currently only has support for Rust and Python clients but working on expanding to node(JS) and C/C++ in the future.

https://github.com/lucidmq/lucidmq

I'm a dev-ops engineer by day. I creating a simple to standup and use message queue(similar to kafka and rabbitmq) in Golang. As of right now, the project is solely to learn more about Go and internals of the commit log.

https://github.com/bdkiran/nolan

General things that could help with this project:

- Single node only, add distributed support(based on raft?)

- Improve or replace the custom protocol for sending and receiving messages(I wrote the current one, it's not pretty)

- Update the CLI to allow for managing topics

If you're interested in contributing to a Go project, in the area of distributed systems check out the repo or send me a message with your ideas.