kratos VS rook

https://github.com/go-kratos/kratos has good examples for project layout

Website: https://go-kratos.dev,

Golang 💪 is a well oiled language for high-performance backend web components. Take Kratos a popular microservices framework.

$ github-compare zeromicro/go-zero go-kratos/kratos asim/go-micro go-kit/kit ┌─────────────────────────┬─────────────────────┬───────────────────────┬──────────────────────┬──────────────────┐ │ METRICS │ ZEROMICRO/GO-ZERO │ GO-KRATOS/KRATOS │ ASIM/GO-MICRO │ GO-KIT/KIT │ ├─────────────────────────┼─────────────────────┼───────────────────────┼──────────────────────┼──────────────────┤ │ 🏠 homepage │ https://go-zero.dev │ https://go-kratos.dev │ https://go-micro.dev │ https://gokit.io │ │ 🌎 language │ Go │ Go │ Go │ Go │ │ 📌 license │ MIT License │ MIT License │ Apache License 2.0 │ MIT License │ │ ⏰ age │ 655 days │ 1231 days │ 2688 days │ 2668 days │ │ 🌟 stars │ 17778(27/d) │ 17856(14/d) │ 18233(6/d) │ 23084(8/d) │ │ 📊 latestDayStarCount │ 33 (up) │ 7 (down) │ 2 (down) │ 10 (up) │ │ 📉 latestWeekStarCount │ 227 (up) │ 64 (down) │ 31 (down) │ 44 (down) │ │ 📈 latestMonthStarCount │ 916 │ 531 │ 176 │ 235 │ │ 👏 forks │ 2520(3/d) │ 3446(2/d) │ 2087(0/d) │ 2315(0/d) │ │ 👀 watchers │ 266 │ 424 │ 510 │ 690 │ │ 💪 issues │ 50/741 │ 51/793 │ 76/914 │ 35/548 │ │ 💯 pull requests │ 13/1155 │ 10/1221 │ 0/1513 │ 9/627 │ │ 👥 contributors │ 132 │ 198 │ 166 │ 221 │ │ 🚀 releases │ 63 │ 49 │ 206 │ 12 │ │ 🔭 release circle(avg) │ 10 days │ 25 days │ 13 days │ 222 days │ │ 🎯 lastRelease │ 24 day(s) ago │ 1 day(s) ago │ 5 day(s) ago │ 8 month(s) ago │ │ 🕦 lastCommit │ 2 day(s) ago │ 2 hour(s) ago │ 5 day(s) ago │ 6 day(s) ago │ │ 📝 lastUpdate │ 47 minute(s) ago │ 16 minute(s) ago │ 1 hour(s) ago │ 1 hour(s) ago │ └─────────────────────────┴─────────────────────┴───────────────────────┴──────────────────────┴──────────────────┘

Kratos errgroup

go-kratos/kratos (Go): Kratos是bilibili开源的一套Go微服务框架，包含大量微服务相关框架及工具。

I have some experience with Ceph, both for work, and with homelab-y stuff.

First, bear in mind that Ceph is a distributed storage system - so the idea is that you will have multiple nodes.

For learning, you can definitely virtualise it all on a single box - but you'll have a better time with discrete physical machines.

Also, Ceph does prefer physical access to disks (similar to ZFS).

And you do need decent networking connectivity - I think that's the main thing people think of, when they think of high hardware requirements for Ceph. Ideally 10Gbe at the minimum - although more if you want higher performance - there can be a lot of network traffic, particularly with things like backfill. (25Gbps if you can find that gear cheap for homelab - 50Gbps is a technological dead-end. 100Gbps works well).

But honestly, for a homelab, a cheap mini PC or NUC with 10Gbe will work fine, and you should get acceptable performance, and it'll be good for learning.

You can install Ceph directly on bare-metal, or if you want to do the homelab k8s route, you can use Rook (https://rook.io/).

Hope this helps, and good luck! Let me know if you have any other questions.

Another option is to leverage a Kubernetes-native distributed storage solution such as Rook Ceph as the storage backend for stateful components running on Kubernetes. This has the benefit of simplifying application configuration while addressing business requirements for data backup and recovery such as the ability to take volume snapshots at a regular interval and perform application-level data recovery in case of a disaster.

This is beyond your question but might help someone else: I switch from docker-compose to kubernetes for my home lab a while ago. The storage solution I've settled on is Rook. It was a bit of up-front work learning how to get it up but now that it's done my storage is automatically managed by Ceph. I can swap out drives and Ceph basically takes care of everything itself.

The stumbling point I am at is I want to use rook.io(Ceph) as my storage solution for the cluster. The Ceph prerequisites are one of the following:

Have you looked at Rook?

I've briefly run ceph in an external mode, you can actually use a rook deployment to manage it (sort of). Here is the documentation for doing that. For me it didn't pass my testing phase because I need better networking equipment before I can try that.

This article explains the data corruption issue happened in Rook in 2021. The root cause lies in an unexpected place and can also occurs in all Ceph environment. It's interesting that Rook had started to encounter this problem recently even though this problem has existed for a long time. It's due to a series of coincidences. I wrote this article because the word "Atari" used in a non-historical context in 2021.

Rook (this is a nice article for Rook NFS)

Storage: Favor any distributed storage you know to start with for Persistent Volumes: Ceph maybe via rook.io, Longhorn if you go rancher etc

I've dealt with a lot of issues that are very close to just unplugging a node. Unfortunately on node lost, my stateful workloads using rook-ceph block storage won't migrate over to another node automatically due to an issue with rook. Stateless apps (ingress nginx, etc..) not using rook-ceph block failover to another node just fine. I've kind of accepted this for now and I know Longhorn has a feature that makes this work but I find rook-ceph to be more stable for my workloads.