Our great sponsors
-
InfluxDB
Power Real-Time Data Analytics at Scale. Get real-time insights from all types of time series data with InfluxDB. Ingest, query, and analyze billions of data points in real-time with unbounded cardinality.
-
minijinja
MiniJinja is a powerful but minimal dependency template engine for Rust compatible with Jinja/Jinja2
-
smithy-rs
Code generation for the AWS SDK for Rust, as well as server and generic smithy client generation.
-
WorkOS
The modern identity platform for B2B SaaS. The APIs are flexible and easy-to-use, supporting authentication, user identity, and complex enterprise features like SSO and SCIM provisioning.
-
avalanche-report
A simple self-hosted web server for creating and managing an avalanche forecast for a region, along with accepting public observations.
I worked on a side project (currently with about 30-50 regular real users) using Rust (with axum), sqlite for the database, minijinja for template rendering, and htmx for the frontend interactivity and S3 for backups. It was quick to hack together (who says Rust is bad for prototyping?), and yet I still feel happy about the code quality. It's been running for a while now in production on fly.io free tier, I noticed it's apparently been using a steady 12MB of RAM, and zero errors or production issues so far since its inception. Last night I decided randomly to benchmark it on my laptop, it can handle 4000+ requests per second hitting the database with a bunch of data inside, I have put almost no effort into optimization. I feel like this might be a good result? Perhaps approaches like this will catch on? Something about this feels pretty cool! Has anyone else had this experience using Rust? I can think of multiple applications (in cluster of microservices) I've come across during my day jobs with large AWS bills and much higher incidental complexity that I would probably choose to do differently given this experience if I had the chance.
Currently https://litestream.io/ but I'm thinking about simplifying deployment further and implementing it manually using AWS SDK without requiring a separate process to manage, as I don't think I really need the WAL streaming features for my particular application.
I worked on a side project (currently with about 30-50 regular real users) using Rust (with axum), sqlite for the database, minijinja for template rendering, and htmx for the frontend interactivity and S3 for backups. It was quick to hack together (who says Rust is bad for prototyping?), and yet I still feel happy about the code quality. It's been running for a while now in production on fly.io free tier, I noticed it's apparently been using a steady 12MB of RAM, and zero errors or production issues so far since its inception. Last night I decided randomly to benchmark it on my laptop, it can handle 4000+ requests per second hitting the database with a bunch of data inside, I have put almost no effort into optimization. I feel like this might be a good result? Perhaps approaches like this will catch on? Something about this feels pretty cool! Has anyone else had this experience using Rust? I can think of multiple applications (in cluster of microservices) I've come across during my day jobs with large AWS bills and much higher incidental complexity that I would probably choose to do differently given this experience if I had the chance.
I worked on a side project (currently with about 30-50 regular real users) using Rust (with axum), sqlite for the database, minijinja for template rendering, and htmx for the frontend interactivity and S3 for backups. It was quick to hack together (who says Rust is bad for prototyping?), and yet I still feel happy about the code quality. It's been running for a while now in production on fly.io free tier, I noticed it's apparently been using a steady 12MB of RAM, and zero errors or production issues so far since its inception. Last night I decided randomly to benchmark it on my laptop, it can handle 4000+ requests per second hitting the database with a bunch of data inside, I have put almost no effort into optimization. I feel like this might be a good result? Perhaps approaches like this will catch on? Something about this feels pretty cool! Has anyone else had this experience using Rust? I can think of multiple applications (in cluster of microservices) I've come across during my day jobs with large AWS bills and much higher incidental complexity that I would probably choose to do differently given this experience if I had the chance.
I worked on a side project (currently with about 30-50 regular real users) using Rust (with axum), sqlite for the database, minijinja for template rendering, and htmx for the frontend interactivity and S3 for backups. It was quick to hack together (who says Rust is bad for prototyping?), and yet I still feel happy about the code quality. It's been running for a while now in production on fly.io free tier, I noticed it's apparently been using a steady 12MB of RAM, and zero errors or production issues so far since its inception. Last night I decided randomly to benchmark it on my laptop, it can handle 4000+ requests per second hitting the database with a bunch of data inside, I have put almost no effort into optimization. I feel like this might be a good result? Perhaps approaches like this will catch on? Something about this feels pretty cool! Has anyone else had this experience using Rust? I can think of multiple applications (in cluster of microservices) I've come across during my day jobs with large AWS bills and much higher incidental complexity that I would probably choose to do differently given this experience if I had the chance.
Something in the lines of https://github.com/jbertovic/svelte-axum-project
Here's an example of what this looks like in practice: https://github.com/awslabs/smithy-rs/tree/main/rust-runtime/aws-smithy-http-server-python/examples
My most recent project is here https://github.com/kellpossible/avalanche-report so probably it will end up looking somewhat similar