gossip-glomers VS mrsk

There's a nice-looking series of exercises from fly.io: https://fly.io/dist-sys/

(I haven't actually done them myself yet, but they look great. Not a standalone resource, but good for practice)

Really worth noting that Maelstrom was the project they used to build the "Fly.io Distributed Systems Challenge" https://fly.io/dist-sys/ which was pretty popular at one point and discussed here, too. https://news.ycombinator.com/item?id=34897723

LiteFS works similarly to async replication you'd find in Postgres or MySQL so it doesn't try to be as strict as something running a distributed consensus protocol like Raft. The guarantees for async replication are fairly loose so I'm not sure Jepsen testing would be useful for that per se.

On the LiteFS Cloud side, it currently does streaming backups so it has similar guarantees but we are expanding its feature set and I could see running Jepsen testing on that in the future. We worked with Kyle Kingsbury in the past on some distributed systems challenges[1] and he was awesome to work with. Would definitely love to engage with him again.

[1]: https://fly.io/dist-sys/

They have really good tech blog posts. Also, they have https://fly.io/dist-sys/

- https://hackattic.com/ : Interesting programming Problems.

- https://sadservers.com/ : Learn Linux by solving problems.

- https://fly.io/dist-sys/ : Distributed Systems Problems.

- https://github.com/pingcap/talent-plan/ : System Programming / Distributed System Challenge.

- https://protohackers.com/ : Server Programming Challenges.

- https://codecrafters.io/ : Implement server tech / softwares from scratch.

- https://hyperskill.org/ : Lots of projects based tutorials.

- https://fly.io/dist-sys/ : Distributed Systems Problems.

Gossip Glomers https://fly.io/dist-sys/ by fly.io is a great way to learn distributed systems. They are fun to solve challenges. zio-maelstrom helps you get started faster in Scala!

There’s also this to practice https://fly.io/dist-sys/

Yeah no the embedded stuff is more a hobby, I'm interested professionally in stuff like what you said you're doing now in another comment, distributed systems and such. Infrastructure for cloud providers, that kind of thing. Right now I'm doing this distributed systems challenge series thing https://fly.io/dist-sys/ which should be cool to put on my github.

Here we'll deploy Anycable wih MRSK.

Honestly these days I am leaning towards this approach: https://github.com/mrsked/mrsk/

It's all just docker.

Did you consider MRSK[1], k3s[2], or dokku[3]? They are all significantly simpler to operate than Kubernetes, curious to hear your take.

[1] https://github.com/mrsked/mrsk

https://github.com/mrsked/mrsk/pull/159 Closed PR about --cache-to option in MRSK

Yes, that thing with the setup is misleading in the docs. I'll make a PR now. There's this issue about it: https://github.com/mrsked/mrsk/issues/301

god or bad, dhh is doing noise and people know about rails. just look at there https://github.com/mrsked/mrsk

I don't think there's a writeup out there, but mrsk just uses docker under the hood. So, if you have a CMD in your Dockerfile, it will use that.

If you have an image that can run multiple things, like a rails app that can run the app process for web traffic by default, but it can also run job workers with the right command, you can provide the cmd in the mrsk config. You can see this in the jobs role in the example: https://github.com/mrsked/mrsk#using-different-roles-for-ser....

You may want to checkout MRSK if you are going to be using docker compose in production on a single VPS https://github.com/mrsked/mrsk

"MRSK basically is Capistrano for Containers, without the need to carefully prepare servers in advance" https://github.com/mrsked/mrsk

https://github.com/mrsked/mrsk might be interesting to you.