consul VS minio

https://github.com/hashicorp/consul/pull/12080 - this should be the Consul issue that brought down Roblox

The Consul collector is production ready! Consul by HashiCorp is a powerful and complex identity-based networking solution, which is not trivial to monitor. We were lucky to have the assistance of HashiCorp itself in this endeavor, which resulted in a monitoring solution of exceptional quality. Look for common blog posts and announcements in the coming weeks!

Changed the service discovery to Consul, since this is the default in JHipster 8.

In another effort to standardize development and operations, Lob has just wrapped up our container orchestration migration from Convox to HashiCorp’s Nomad, led by Senior Platform Engineer Elijah Voigt. In this new ecosystem, one feature available to us is Consul Service Mesh (a feature of Consul, which is part of our Lob Nomad stack).

Service registry and discovery etcd, consul, nacos

The underlying tool Consul is very powerful, and Consul Connect service mesh on top of this tool is quite robust and extremely flexible where you can swap out the default CA for other solutions, like Vault CA, and swap out the Envoy proxy for another solution, like NGINX or HAProxy. For ingress into the cluster, you can use Consul API Gateway, or another API Gateway or an ingress controller.

I'd like to also mention hashicorp nomad + consul. They're worth evaluating.

Out of the number of service mesh solutions that exist, the most popular open source ones are: Linkerd, Istio, and Consul. Here at Koyeb, we are using Kuma.

Consul

A service mesh provides features to help with common distributed microservice challenges. Like service discovery, routing, load balancing, and so on. Today we will be using Istio, one of the most popular service mesh solutions available. Istio is tailored for distributed application architectures, especially those you might run in Kubernetes. Istio plays nicely with Kubernetes, so nicely that you might think that it's part of the Kubernetes platform itself. Istio isn't the only service mesh around; we also have platforms like Linkerd and Consul, which are also quite popular.

On a related note, does anyone know what happened to the minio edge command mentioned here? They said that S3 gateway will live on as minio edge, but gateway was removed and edge is nowhere to be found.

On the other hand, 2GB RAM is quite useful for server-type workload: A web server, a small DB, a blog, email service...what other people buy RPi's for, you can do with that laptop. Add some external (USB3 I hope) storage (SSD or even a good USB stick), and use it as centralized storage. I run minio (S3 storage) and NextCloud on a small machine and it's way more convenient and useful than I imagined initially.

A good place to start this discussion would be https://github.com/minio/minio/issues

Without your setup details we are just guessing. You can post your setup here: https://github.com/minio/minio/discussions

Minio

You can host your own S3 API-compatible object storage service on some EC2 instances (exercise left to the reader to figure out how to make that reliable). Zero PUT cost, higher operational overhead.

  Minio: https://github.com/minio/minio

Sometimes it's pretty cut and dry, just people using open source without attribution and hoping that nobody will find out. But why?

MinIO seems to be licensed under AGPL: https://github.com/minio/minio/blob/master/LICENSE

It seems that it effectively mandates that the modified version needs to be made available: https://en.wikipedia.org/wiki/GNU_Affero_General_Public_Lice...

  The GNU Affero General Public License is a modified version of the ordinary GNU GPL version 3. It has one added requirement: if you run a modified program on a server and let other users communicate with it there, your server must also allow them to download the source code corresponding to the modified version running there.