#Rust sqlite code#

Oso Cloud stores roles, relations, and permissions. This takes time, but hasn’t been a reason to switch away from using Rust. We’ve built custom integrations with Segment.io and Honeycomb.io because there were no existing libraries that covered our needs. We’ve had to build a lot of things ourselves, like Github OAuth. There are lots of things you would take for granted in a more mature web ecosystem like Django or Rails that you end up having to do yourself in Rust. The Rust programming ecosystem is pretty new. There’s no need to check headers or see if fields are null, or anything like that in our handlers. When we say a handler takes a logged-in user and a certain struct, we know that Rocket will make sure all the data is as we’ve described before it calls us. This drastically cuts down on the amount of “defensive programming” we have to do. It then uses those types (with some help from the serializing-deserializing library Serde) to take care of all the up-front validation before calling the handler. Rocket has some magical type macros that let us specify the inputs to our request handlers as normal Rust structs. It uses async Rust and does a lot of our work for us. Rocket is a web framework that is built on top of Tokio. Async’s improvements made it an easy choice for us to go with Rocket.

#Rust sqlite code#

Async, thankfully, makes that kind of code a lot easier to read. When writing this new service, we expected to have to write those long chains of futures with and_then and map_err and all kinds of hard-to-follow combinators. But a lot had changed since we last looked! For instance, we’d built an old service with Tokio, but that was before async. We had built Rust web stuff in the past and, to be honest, the experience wasn’t too great. Also, it would let the Polar core and the new service be a unified code base without an FFI layer between them.

This meant we needed to build some new web APIs and also add a data store. The new service uses the same Polar core as the library but combines it with APIs to manage roles, relationships and permissions. To learn more about how Oso Cloud works, you can check out Oso Cloud’s own documentation. It also means you can use Polar in languages we don’t yet have libraries for, like C# and PHP. This service architecture lets us build new features easily, like the ability to make authorization decisions based on data from multiple services (which is useful for customers’ microservice architectures), better role management, and tools to help build policies. Instead of embedding it in a library, we've moved it to a service that multiple other services can use. Recently we've been working on a new way to use Polar. Rust is a great language to build a language in, and using Rust made it easy for us to embed Polar in other languages as part of the Oso library. We wrote the core of Oso, the Polar language, in Rust. How we use Rust, SQLx and Rocket for Oso Cloud