top | item 28129159

Rust in Production: Qovery

127 points| aroccoli | 4 years ago |serokell.io

26 comments

[+] icholy|4 years ago|reply

Unfortunate name ...

[+] cdcarter|4 years ago|reply

Yea, super weird name....

[+] JimTheMan|4 years ago|reply

As in Q-ovary? I don't think that's the end of the world, even if it meant to be pronounced as such.

[+] Santosh83|4 years ago|reply

It's unsure exactly how to pronounce it. And because of that, there is also the risk you could misspell it.

[+] aroccoli|4 years ago|reply

Why so?

[+] pojon|4 years ago|reply

How hard is it to set up build caches? Does anyone have working examples for toy projects?

[+] rhooke|4 years ago|reply

I'm not sure what you mean by a build cache, does sccache suit?

https://github.com/mozilla/sccache

[+] staticassertion|4 years ago|reply

It's pretty simple to use sccache, which is what we do.

[+] dom_hutton|4 years ago|reply

Spoke to the founder recently chasing a job there, great team and a great attitude. Talented people should reach out!

[+] hu3|4 years ago|reply

> As of today, Qovery CLI (CLI used by devs to interact with Qovery) and Pleco (a tool allowing us to clean old cloud resources) are written in Go, and Qovery backend is mostly written with Kotlin.

This is great engineering. Sensible use of technology.