K3s is another compact Kubernetes distribution. Developed by SUSE, it's packaged as a single binary that comes in at less than 70MB. Despite this tiny footprint, K3s is certified as compatible with upstream Kubernetes, is ready for production use, and supports high availability. - Source: dev.to / 19 days ago

For self-hosting I've found https://k3s.io to be really good from the SUSE people. Works on basically any Linux distro and makes self-hosting k8s not miserable. - Source: Hacker News / 3 months ago

K3S: is a lightweight distribution of Kubernetes that is designed for resource-constrained environments. It is an excellent option for running Kubernetes on a virtual machine or cloud server. - Source: dev.to / 5 months ago

I recently purchased a used Lenovo M900 Think Centre (i7 with 32GB RAM) from eBay to expand my mini-homelab, which was just a single Synology DS218+ plugged into my ISP's router (yuck!). Since I've been spending a big chunk of time at work playing around with Kubernetes, I figured that I'd put my skills to the test and run a k3s node on the new server. While I was familiar with k3s before starting this project,... - Source: dev.to / 7 months ago

I’ve created a local cluster with K3S and installing Windmill could not be simpler with just one chart to configure, which already has sane defaults to get started. For this demo we will also configure workers to passthrough environment variables to our scripts so that they have access to the Kubernetes API server for later. - Source: dev.to / 7 months ago

I also read that Salt was using MessagePack to format their messages. MessagePack is a format like JSON, but more compact. - Source: dev.to / 9 months ago

So appreciate such a detailed reply, thanks. btw, why did you choose tinylib/msgp from 4 available go-impls? Source: over 1 year ago

If you find you're running the serial connection at maximum speed and it's still not fast enough, try switching to a more compact binary encoding that has both Serde and Arduino implementations, like MsgPack... Though I don't remember enough about its format off the top of my head to tell you the easiest way to put an unambiguous header on each packet/message to make the protocol self-synchronizing. Source: over 1 year ago

The information can be stored in a database or as files, serialized in a standard format and with a schema agreed with your Data Engineering team. Depending on your information and requirements, it can be as simple as CSV, XML or JSON, or Big Data formats such as Parquet, Avro, ORC, Arrow, or message serialization formats like Protocol Buffers, FlatBuffers, MessagePack, Thrift, or Cap'n Proto. - Source: dev.to / over 1 year ago

MessagePack Similar to JSONs, just more compact, although not as much as the ones above. Still, it's usefull to retain some readability in your messages. Source: over 1 year ago