3 ms·

What are you building with Rust if you don’t mind sharing? I’m curious to know what sorts of companies are using it out there in production.

ekidd 8y ago
Here are the major categories of stuff we've built in Rust at work: 1. Lots of little CLI tools, statically linked using https://github.com/emk/rust-musl-builder https://github.com/emk/rust-musl-builder. These are fast, portable, easy to share, and easy to add to Docker containers. For a fun open source example, see https://github.com/faradayio/geochunk https://github.com/faradayio/geochunk, which groups US zip codes into evenly-sized chunks. 2. Code where we need to handle all the corner cases very carefully. Rust's enum and match are wonderful for this. An older open source example would be https://github.com/faradayio/cage https://github.com/faradayio/cage, which performed all sorts of fiddly transformations on docker-compose.yml files. (I need to massively overhaul this to work with https://kustomize.io/ https://kustomize.io/ someday.) 3. Code which moves around large amounts of data, and maybe processes some of it. This might involve REST APIs, AMQP queues, cloud buckets or databases. Sometimes we wind up writing a little extra glue code, but we're pretty happy overall. This morning, I'm working on an unreleased open source command-line tool that moves large database tables between different local and cloud databases. This actually uses async Rust (specifically https://tokio.rs/blog/2018-08-async-await/ https://tokio.rs/blog/2018-08-async-await/), which is definitely bleeding edge. But this particular code benefits enormously from Tokio, so we're taking the plunge. Overall, our Rust code is fast and reliable. I enjoy working on it, and my boss likes the fact that our Rust code tends to be very solid.
deleted 8y ago
[deleted]
js2 8y ago
Sentry is using it to help their Python backend to process crash reports: https://github.com/getsentry/symbolic https://github.com/getsentry/symbolic
pimeys 8y ago
In my previous job I wrote a push notification service[0] and a high traffic web server[1] with Rust. Both were rock solid and fast. Now at https://www.prisma.io/ https://www.prisma.io/ we're converting our Scala codebase one module at a time to Rust, plugging them to the Scala codebase with JNA until all the code is converted. Plan is to have better portability between different languages and smaller resource usage. With Rust, interfacing other languages such as Java/Scala, Javascript and so on is quite ergonomic. I also saw Kraken cryptocurrency exchange looking for Rust developers to help with transition, so it seems there is some work opportunities already in the field. [0] https://github.com/xray-tech/xorc-notifications https://github.com/xray-tech/xorc-notifications [1] https://github.com/xray-tech/xorc-gateway https://github.com/xray-tech/xorc-gateway

ekidd 8y ago

Here are the major categories of stuff we've built in Rust at work: 1. Lots of little CLI tools, statically linked using https://github.com/emk/rust-musl-builder https://github.com/emk/rust-musl-builder. These are fast, portable, easy to share, and easy to add to Docker containers. For a fun open source example, see https://github.com/faradayio/geochunk https://github.com/faradayio/geochunk, which groups US zip codes into evenly-sized chunks. 2. Code where we need to handle all the corner cases very carefully. Rust's enum and match are wonderful for this. An older open source example would be https://github.com/faradayio/cage https://github.com/faradayio/cage, which performed all sorts of fiddly transformations on docker-compose.yml files. (I need to massively overhaul this to work with https://kustomize.io/ https://kustomize.io/ someday.) 3. Code which moves around large amounts of data, and maybe processes some of it. This might involve REST APIs, AMQP queues, cloud buckets or databases. Sometimes we wind up writing a little extra glue code, but we're pretty happy overall. This morning, I'm working on an unreleased open source command-line tool that moves large database tables between different local and cloud databases. This actually uses async Rust (specifically https://tokio.rs/blog/2018-08-async-await/ https://tokio.rs/blog/2018-08-async-await/), which is definitely bleeding edge. But this particular code benefits enormously from Tokio, so we're taking the plunge. Overall, our Rust code is fast and reliable. I enjoy working on it, and my boss likes the fact that our Rust code tends to be very solid.

deleted 8y ago

[deleted]

js2 8y ago

Sentry is using it to help their Python backend to process crash reports: https://github.com/getsentry/symbolic https://github.com/getsentry/symbolic

pimeys 8y ago

In my previous job I wrote a push notification service[0] and a high traffic web server[1] with Rust. Both were rock solid and fast. Now at https://www.prisma.io/ https://www.prisma.io/ we're converting our Scala codebase one module at a time to Rust, plugging them to the Scala codebase with JNA until all the code is converted. Plan is to have better portability between different languages and smaller resource usage. With Rust, interfacing other languages such as Java/Scala, Javascript and so on is quite ergonomic. I also saw Kraken cryptocurrency exchange looking for Rust developers to help with transition, so it seems there is some work opportunities already in the field. [0] https://github.com/xray-tech/xorc-notifications https://github.com/xray-tech/xorc-notifications [1] https://github.com/xray-tech/xorc-gateway https://github.com/xray-tech/xorc-gateway