tikv VS diesel

TiKV: basis data key-value transaksional yang terdistribusi.

Before I introduce this phase, I'd like to talk about the batch system. It is the cornerstone of TiKV's multi-raft implementation.

TiKV is a distributed key-value storage engine, which is based on the designs of Google Spanner, F1, and HBase. However, TiKV is much simpler to manage because it does not depend on a distributed file system.

Last time i looked into it there weren't that many i could find. There is https://github.com/tikv/tikv which uses rocksdb with raft. and there is faster https://github.com/microsoft/FASTER/ .

There is also https://tikv.org/ but I don't know how well it scales down to be embedded in the server, like sqlite or rocksdb.

tikv/tikv (Rust): Distributed transactional key-value database, originally created to complement TiDB

A web application wont be complete without one, using a nifty tool called diesel we'll be able to create database tables, schemas and make queries in Rust but first we need a database installed, ill be using postgresql, also make sure you install just the postgresql feature of diesel.

Resources https://github.com/diesel-rs/diesel/blob/master/guide_drafts/trait_derives.md

I initially meant to use Rails as a way to learn it, but missed Rust too much and switched to Yew for the frontend and Diesel and Tide for the backend. I'm trying to force myself to care more about finishing the project (and quickly getting it into production!) than making everything perfect, which is difficult for me.

Diesel is quite nice for SQL imo, but some don't like it. I'd recommend at least giving it a try.

You may find it easier to use threaded rouille HTTP server running on Heroku (with heroku-buildpack-rust) and store the images as Postgres Large Objects. Heroku backs up the database automatically, so you don't need to worry about a random machine failure destroying the photos while you're on your honeymoon.

I'm not building web-apps yet, currently i'm doing a terminal UI app. You can check the cargo.toml for deps. I'm planning to build a Rust blueprint for JHipster quite soon so I'll be able to directly compare productivity with Spring boot. And yes there is no equivalent of SB in Rust but I don't think you need that in Rust, there are great web frameworks like Actix or Rocket which provides most of what you need from SB and since you dont have to do OOP in Rust you actually dont need many Hibernate like features IMO, but you have http://diesel.rs/ to cover that.

I managed to install the diesel cli like they showed on the getting started page, but when I try to run the diesel commands from command promt I get an error box that pops up saying: "The application was unable to start correctly (0xc000007b). Click OK to close the application." Apparently there was a similar issue previously (https://github.com/diesel-rs/diesel/issues/2034) but they just said its probably some missing DLLs but how do I know what DLLs are missing? Any ideas on how to fix this issue?

let results = posts .filter(published.eq(true)) .limit(5) .load::(&connection) .expect("Error loading posts"); Link to full source

Planning to finish up the derive syntax refactor in diesel. https://github.com/diesel-rs/diesel/pull/2626

The technology stack of Juniper and Actix to build a GraphQL server is probably the best way to do it in Rust right now, even though Juniper is still pretty much in development where API changes are common. In practice, you would usually have a database, where Diesel is used. The way of creating a GraphQL schema via code is also not always the preferred way. Svelte is interesting to work with, had pretty much no dependencies to install and compiled fast.