>From a general philosophical perspective, I think the health of our ecosystem >would be better served by having one core natively compiled driver lib and >then language ecosystem native wrappers around that core. Similarly to how the >Swift driver wraps the C++ driver. Lowering the amount of engineering required >to keep multiple language ecosystem drivers in parity is a big win as the >ecosystem's currently pretty fragmented.
Using rust for the core of that given its memory safety, concurrency correctness, performance, language interconnect ecosystem, and general zeitgeist makes a lot of sense to me. On Tue, Feb 3, 2026, at 2:21 PM, Bret McGuire wrote: > Greetings all! > > Another one that seemed worthwhile to bring to the list. I've just filed > CASSPYTHON-8 <https://issues.apache.org/jira/browse/CASSPYTHON-8> to explore > the idea of replacing our current C and cython code with equivalent Rust > implementations. This technique is becoming more common in the Python world > but there are concrete benefits for us on the Python driver team. There's > some discussion about these benefits on CASSPYTHON-8. > > Our upcoming release (likely 3.30.0) will be intended to get an > ASF-branded Python driver out into the wild so I'm not planning on tackling > any work in this area then. The plan would be to start with this effort for > 3.31.0. We'll start with something small, just to try out the mechanism for > integrating Rust code into a Python project, and see where that takes us. > > Thanks! > > - Bret -
