-
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.
-
-
-
-
SaaSHub
SaaSHub - Software Alternatives and Reviews. SaaSHub helps you find the best software and product alternatives
Some time ago I've created a language where the main design goal was for it to be easy to use and embed: https://github.com/kgabis/ape.
I agree; wasm would be a better choice, as it's specifically designed for this use case. RISC-V is designed for hardware implementation, not to be an IR, which means that things are more verbose than they need to be. For example, accessing an arbitrary 64-bit address requires 6 instructions [1] in RISC-V, whereas in Wasm you can just do it. Even more important than ISA differences, though, is that with Wasm you get WASI, which saves you a whole lot of time creating a sandboxed system interface.
[1]: https://github.com/riscv-non-isa/riscv-elf-psabi-doc/pull/38...
I think this practice is generally good for "most fast things" I noticed that [ksimple](https://github.com/kparc/ksimple/blob/31370a2c799a2a0e491d52...) uses this approach too (this is the core of the k apl which is used in finance and engineering industries so very fast for data processing applications. Not sure how it fares in a more general setting but wouldn't be surprised if it was also competitive.