Readit News logoReadit News
tamalsaha001 commented on RabbitMQ 4.0   github.com/rabbitmq/rabbi... · Posted by u/rhodin
packetlost · a year ago
None of them are close. RabbitMQ has traffic shaping, MQ->MQ routing (federation), and all sorts of stuff that is super important if you use it as a generalized routing system (vs plain IP). NATS doesn't have that and it's almost certainly firmly out of scope.
tamalsaha001 commented on Launch HN: Spinach.io (YC W22) – Better daily standups    · Posted by u/talmi
tamalsaha001 · 3 years ago
We have been using https://www.dailybot.com (another YC company) for the last 2-3 years. That one is great, too!
tamalsaha001 commented on Build Your Own X   github.com/codecrafters-i... · Posted by u/pretext
poochkoishi728 · 4 years ago
If you follow a guide or conceptually learn how write X, and write your own version of GPL code, are you now free from copyright restrictions?
tamalsaha001 · 4 years ago
Yes, if you have done a clean room implementation.
tamalsaha001 commented on NSA Kubernetes Hardening Guidance [pdf]   media.defense.gov/2021/Au... · Posted by u/kennethko
pletnes · 5 years ago
What yields the lowest risk - spending a ton of time hardening one cluster, or building multiple clusters to reduce the blast radius of bugs and misconfigurations?
tamalsaha001 · 5 years ago
Both for different reasons!
tamalsaha001 commented on Cue, an open-source data validation language   cuelang.org/docs/about/... · Posted by u/benhoyt
wikibob · 5 years ago
Some context:

Cue is a project originally started by Marcel van Lohuizen who previously was part of BCL (Borg Config Lang) at Google. The main use is to generate config files.

See the Kubernetes examples at: https://cuelang.org/docs/tutorials/

Here are two posts discussing the motivations for Cue over BCL/Jsonnet:

- https://github.com/cuelang/cue/issues/33#issuecomment-483615...

- https://github.com/cuelang/cue/discussions/669

A very interesting development is that Grafana appears to be adopting Cue as a first-class configuration option. See: "Bring new CUE-based config schema system to release-readiness" https://github.com/grafana/grafana/issues/33139

This could mean that a future where Grafana dashboards can be two-way synced with a git repo will eventually exist.

----

Other tools with some industry adoption in the "Infrastructure as Code" space include

- Dhall

- Jsonnet (from BCL)

- kustomize

- Helm

- kubecfg

- Tanka

- SkyCfg

- jkcfg

- Krane

- HCL (Terraform)

And two tools that fall into a separate class of enabling "Infrastructure as Software"

- Pulumi (TypeScript/Go/Python/.NET)

- CDK

tamalsaha001 · 5 years ago
It might sound a bit pedantic, but kustomize strictly avoids the "Infrastructure as Code" space and stays in the "Infrastructure as Data" space. The main difference is that since it just deals with "data", you can build any higher level tooling on this. One of the major proponents of this idea is Brian Grant from Google. He tweets about this from time to time. Here is a recent one: https://twitter.com/bgrant0607/status/1404461906186833927
tamalsaha001 commented on Grafana, Loki, and Tempo will be relicensed to AGPLv3   grafana.com/blog/2021/04/... · Posted by u/WalterSobchak
188201 · 5 years ago
I think that's misunderstanding of AGPL. For internal use, AGPL does not require to share the proprietary part.

If a company develop an proprietary UI and use Loki as backend, this is not serving Loki directly to customer, so that does not require company to release their code.

It is similar to GPL. Dynamic linking to a GPL software does not require the developer releasing their code.

Only provider serving Loki instance directly to customer required to share the code.

Only Amazon is upset that they cannot just host a popular open source project directly on their cloud. Maybe they could pay a license fee for dual licensing arrangement, which is a better way to support open source startup.

tamalsaha001 · 5 years ago
That does not seem to be the case. From [1]

The difference between the AGPL and traditional GPL is simple: The AGPL seeks to close a "loophole" that allows a company or organization to modify GPL'ed software and use it to provide a service — but without actually distributing changes. So a company can take a package like, say, WordPress and modify the software significantly to sell a service — but hold back changes because it's not technically "distributing" or "propagating" the software. The AGPL goes a bit further and says that if the program is "intended to interact with users through a computer network" and if the version that you received gives users "the opportunity to request transmission to that user of the Program's complete source code," you have to maintain that functionality and distribute the modified version.

[1] https://www.networkworld.com/article/2229265/is-the-affero-g...

u/tamalsaha001

KarmaCake day324September 5, 2012
About
[ my public key: https://keybase.io/tsaha; my proof: https://keybase.io/tsaha/sigs/3dXTTpGomQgN0Xn5OwpANseI1tXC49gT0qP4UkMz45k ]

Founder & CEO at appscode.com . Builder of KubeDB, Stash, KubeVault, Kubeform, Voyager.

View Original