vmarchaud
Joined 9 years ago
Joined 9 years ago
> We only accept formulae that use a Debian Free Software Guidelines license or are released into the public domain following DFSG Guidelines on Public Domain software into homebrew/core.
[0]: https://vmarchaud.fr/deploying-kubernetes-the-hard-way/
[0]: https://github.com/kubernetes-sigs/kubespray
[1]: https://www.tauceti.blog/
[2]: https://www.tauceti.blog/posts/kubernetes-the-not-so-hard-wa...
[3]: https://k3s.io/
[5]: https://vmarchaud.fr/deploying-kubernetes-the-hard-way/
That's not actually something you can do much about considering the sheer size of opentelemetry (both in term of implementation and vendors working on it) and i expect for people implementing nowadays, proto should be pretty stable and my experience should theorically not be the case anymore.
[0]: https://github.com/open-telemetry/oteps/pull/171
[1]: https://github.com/open-telemetry/opentelemetry-proto/pull/3...
[0]: https://docs.google.com/document/d/1ZJZbv4J6FZ8Dnb0JuMhJxTnw...
Why use WASM ? Because we wanted to stay close to our stack (ie. calling wasm from nodejs). Do it work ? Yes, memory consumption is quite heavy though (each WASM module have its own heap that can quickly grow).
However we are looking to directly use Skia now and avoid the overhead of WASM so i think its a nice solution in the beginning but you might want to ditch it later on.
[0]: https://github.com/google/skia/tree/main/modules/canvaskit
Not exactly related but we had issues with the official openapi generated so he also wrote a package to codegen typescript client from an openapi file [3]
[0]: https://github.com/lukeautry/tsoa/pulls?q=is%3Apr+sort%3Aupd...
[1]: https://github.com/Eywek/typoa
We already had experience with running bare metal infra (hashicorp stack), currently evaluating how to deploy it (currently using GKE). Althrough it should be straight forward since its mostly stateless workload, we it need to be able scale x10 in less than 1h sometimes so we might throw an node autoscaler that provision from cloud.
Contact: contact@<username>.fr