HackerReposA FIELD GUIDE TO OPEN SOURCE
ProSponsor the shelf♧ 0
← Back to top all-time
second-state
microservice-rust-mysql
Rust2022–2023
second-state / microservice-rust-mysql

microservice-rust-mysql

A template project for building a database-driven microservice in Rust and run it in the WasmEdge sandbox.

4Distinct people
5Mentions
0Explicit recommenders
372GitHub stars
REPOSITORY AT A GLANCE

What to know before exploring

What it is

A template project for building a database-driven microservice in Rust and run it in the WasmEdge sandbox.

GitHub

Where it is used

No documented product use has been verified yet.

What people are saying

No recommendation phrase was found in the indexed comments.

No classified warning is attached to this page. Read the discussions before treating silence as approval.

Also in these discussions

Mentioned in the same Hacker News threads. That is not proof they are substitutes.

This week on Hacker News

Nov 7–Nov 14 UTC · Direct repository links and separately labeled related project stories. Indexed through 11/14/2026, 3:56:07 PM UTC.

No direct repository links were found in the indexed HN discussions over the past seven days. Older discussions are available below.

Mentions over time

HN mentions by week5 dated mentions

Observed mentions: 2022-10-25 11:34:15 UTC to 2023-05-29 06:33:33 UTC. Weeks start Monday, UTC.

01232022-10-24 00:00:00 UTC to 2022-10-31 00:00:00 UTC (exclusive): 3 mentions; 1 submissions, 2 commentsOct 242022-10-31 00:00:00 UTC to 2022-11-07 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2022-11-07 00:00:00 UTC to 2022-11-14 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2022-11-14 00:00:00 UTC to 2022-11-21 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2022-11-21 00:00:00 UTC to 2022-11-28 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2022-11-28 00:00:00 UTC to 2022-12-05 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2022-12-05 00:00:00 UTC to 2022-12-12 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2022-12-12 00:00:00 UTC to 2022-12-19 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2022-12-19 00:00:00 UTC to 2022-12-26 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2022-12-26 00:00:00 UTC to 2023-01-02 00:00:00 UTC (exclusive): 1 mentions; 1 submissions, 0 comments2023-01-02 00:00:00 UTC to 2023-01-09 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2023-01-09 00:00:00 UTC to 2023-01-16 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2023-01-16 00:00:00 UTC to 2023-01-23 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2023-01-23 00:00:00 UTC to 2023-01-30 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2023-01-30 00:00:00 UTC to 2023-02-06 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2023-02-06 00:00:00 UTC to 2023-02-13 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 commentsFeb 62023-02-13 00:00:00 UTC to 2023-02-20 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2023-02-20 00:00:00 UTC to 2023-02-27 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2023-02-27 00:00:00 UTC to 2023-03-06 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2023-03-06 00:00:00 UTC to 2023-03-13 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2023-03-13 00:00:00 UTC to 2023-03-20 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2023-03-20 00:00:00 UTC to 2023-03-27 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2023-03-27 00:00:00 UTC to 2023-04-03 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2023-04-03 00:00:00 UTC to 2023-04-10 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2023-04-10 00:00:00 UTC to 2023-04-17 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2023-04-17 00:00:00 UTC to 2023-04-24 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2023-04-24 00:00:00 UTC to 2023-05-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2023-05-01 00:00:00 UTC to 2023-05-08 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2023-05-08 00:00:00 UTC to 2023-05-15 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2023-05-15 00:00:00 UTC to 2023-05-22 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2023-05-22 00:00:00 UTC to 2023-05-29 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2023-05-29 00:00:00 UTC to 2023-06-05 00:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 commentsMay 29

Counts come from the repository’s dated source evidence. Index cutoff: 2026-11-02 08:16:59 UTC.

View mention counts and date ranges
UTC ranges include their start and exclude their end. Select a period to filter the source evidence.
PeriodStart (UTC)End (exclusive, UTC)MentionsSubmissionsComments
Oct 242022-10-24 00:00:00 UTC2022-10-31 00:00:00 UTC312
Oct 312022-10-31 00:00:00 UTC2022-11-07 00:00:00 UTC000
Nov 72022-11-07 00:00:00 UTC2022-11-14 00:00:00 UTC000
Nov 142022-11-14 00:00:00 UTC2022-11-21 00:00:00 UTC000
Nov 212022-11-21 00:00:00 UTC2022-11-28 00:00:00 UTC000
Nov 282022-11-28 00:00:00 UTC2022-12-05 00:00:00 UTC000
Dec 52022-12-05 00:00:00 UTC2022-12-12 00:00:00 UTC000
Dec 122022-12-12 00:00:00 UTC2022-12-19 00:00:00 UTC000
Dec 192022-12-19 00:00:00 UTC2022-12-26 00:00:00 UTC000
Dec 262022-12-26 00:00:00 UTC2023-01-02 00:00:00 UTC110
Jan 22023-01-02 00:00:00 UTC2023-01-09 00:00:00 UTC000
Jan 92023-01-09 00:00:00 UTC2023-01-16 00:00:00 UTC000
Jan 162023-01-16 00:00:00 UTC2023-01-23 00:00:00 UTC000
Jan 232023-01-23 00:00:00 UTC2023-01-30 00:00:00 UTC000
Jan 302023-01-30 00:00:00 UTC2023-02-06 00:00:00 UTC000
Feb 62023-02-06 00:00:00 UTC2023-02-13 00:00:00 UTC000
Feb 132023-02-13 00:00:00 UTC2023-02-20 00:00:00 UTC000
Feb 202023-02-20 00:00:00 UTC2023-02-27 00:00:00 UTC000
Feb 272023-02-27 00:00:00 UTC2023-03-06 00:00:00 UTC000
Mar 62023-03-06 00:00:00 UTC2023-03-13 00:00:00 UTC000
Mar 132023-03-13 00:00:00 UTC2023-03-20 00:00:00 UTC000
Mar 202023-03-20 00:00:00 UTC2023-03-27 00:00:00 UTC000
Mar 272023-03-27 00:00:00 UTC2023-04-03 00:00:00 UTC000
Apr 32023-04-03 00:00:00 UTC2023-04-10 00:00:00 UTC000
Apr 102023-04-10 00:00:00 UTC2023-04-17 00:00:00 UTC000
Apr 172023-04-17 00:00:00 UTC2023-04-24 00:00:00 UTC000
Apr 242023-04-24 00:00:00 UTC2023-05-01 00:00:00 UTC000
May 12023-05-01 00:00:00 UTC2023-05-08 00:00:00 UTC000
May 82023-05-08 00:00:00 UTC2023-05-15 00:00:00 UTC000
May 152023-05-15 00:00:00 UTC2023-05-22 00:00:00 UTC000
May 222023-05-22 00:00:00 UTC2023-05-29 00:00:00 UTC000
May 292023-05-29 00:00:00 UTC2023-06-05 00:00:00 UTC101

What Hacker News says

5 sources
https://github.com/WasmEdge/WasmEdge/releases/tag/0.12.1 Key features: * New plugin system makes it easy for community to add features to WasmEdge * New Wasm APIs for AI, observability and networking through plugins * Advanced socket networking * Better embedding through improved host SDKs * Performance and compatibility enhancements The WasmEdge plugin API provides an easy way to add, manage and package host functions into the runtime. All host capabilities, including WASI itself, are now plugins in WasmEdge. That means you can even swap in a new WASI implementation (eg for a real-time OS). You can write plugins in C, C++ and Rust! Those plugins will be compatible with the component model making them future proof! https://wasmedge.org/docs/contribute/plugin/intro Some examples: WasmEdge’s Tensorflow Lite plugin enables lightweight (1/10
Read the rest
of Linux containers) and fast (native GPU) AI inference apps for Tensorflow Lite models. https://wasmedge.org/docs/develop/rust/ai_inference/tensorfl... WasmEdge’s PyTorch plugin enables lightweight (1/10 of Linux containers) and fast (native GPU) AI inference apps for PyTorch models. https://wasmedge.org/docs/develop/rust/ai_inference/pytorch/ Through the new WasmEdge plugin system, the community are adding support for libraries like zlib, OpenCV, tesseract and ffmpeg etc. Putting these together, we are supporting complex AI libraries such as Mediapipe on WasmEdge! https://github.com/yanghaku/mediapipe-rs The Mediapipe story is esp interesting since WasmEdge is now adapted as a runtime for stream data process in products like Fluvio, Redpanda, YoMo, RisingWave and others. Mediapipe support allows developers to add AI into the stream data pipeline. https://github.com/xxchan/fluvio/pull/1 WasmEdge’s eBPF plugin enables developers to create secure and containerized eBPF tools and controllers in Kubernetes environments. https://github.com/WasmEdge/WasmEdge/tree/master/plugins/was... A good example of WasmEdge 0.12.1 WASI enhancement is the ability to limit the Wasm app to read-only access to files and folders. WasmEdge sockets API is refactored in 0.12.1 to be compatible with the much more limited WASI socket proposal. WasmEdge sockets have become a super set of WASI sockets. The WasmEdge networking sockets got new features in version 0.12.1, such as DNS, network device binding and TLS. You will be able to create sophisticated microservices that require highly-efficient non-blocking network sockets. https://github.com/second-state/wasmedge_wasi_socket Here are several complex networking applications possible with WasmEdge sockets. https://github.com/second-state/microservice-rust-mysql https://github.com/WasmEdge/wasmedge-db-examples https://github.com/WasmEdge/wasmedge_hyper_demo WasmEdge is already one of the smallest and most efficient Wasm runtimes out there. It embeds into libsql (SQLite on the server!) to execute user definited functions to perform complex tasks like HTTPS web services & AI inference from SQL statements! https://wasmedge.org/docs/embed/use-case/libsql/ The WasmEdge C++ and Rust SDKs allow host applications to embed Wasm functions asynchronously. It is critically important in many applications where the embedded Wasm function is simply not allowed to block the execution of the host applications. https://github.com/second-state/wasmedge-rustsdk-examples/bl... Asynchronous host SDKs are complex and a lot of work still remains. We are continuously improving it with our end user and partner communities. Preview: https://github.com/L-jasmine/WasmEdge/tree/feat/async What's coming next? * Support plugins in our Docker and k8s integrations * Wasm GC support for languages like Kotlin and Dart * WASI thread * Stack switching for coroutines * Component model * Support for inference on open source LLMs * Better JS & Python support for AI
In Release: WasmEdge 0.12 and 0.12.1
Great question! In the demo app we showed yesterday (source here - https://github.com/second-state/microservice-rust-mysql), the Dockerfile is leveraging a multi-stage build where the first stage builds the Wasm module and the second stage extracts the Wasm module into a "FROM scratch" image. In Compose, the "server" service is running using the image that is produced by that build. It's then handed off to the new Wasm runtime, where the module is extracted and executed. Hope that helps! Feel free to follow up with more questions!
In The Docker+WASM Technical Preview
3Sophons·Oct 25, 2022Submission

A complete microservice backed by MySQL, written in Rust and compiled into WASM

Here is a complete microservice backed by a MySQL database. It is written in Rust, compiled into WebAssembly and runs entirely in the WasmEdge sandbox. Why & how? https://github.com/second-state/microservice-rust-mysql WasmEdge is a cross-platform WebAssembly runtime for cloud native apps. For Rust and JS apps, it is a much lighter, faster, and more secure alternative to Linux containers. It is perfect for microservices and serverless functions. In the context of microservices, WasmEdge can be managed by existing container toolchains. In a Kubernetes cluster, WasmEdge apps can run side-by-side with Linux container apps. WasmEdge apps can be managed by container tools like Podman and the Docker Desktop and CLI (more on this next week!). Here is how to use Podman to start / manage WasmEdge: https://github.com/KWasm/podman-wasm Now back to
Read the rest
the microservice itself. It provides a lightweight yet very fast web server to handle JSON over HTTP requests. It is based on the popular Rust tokio, hyper, and serde libraries. See more examples: https://github.com/WasmEdge/wasmedge_hyper_demo The microservice also features an async MySQL client to interact with backend databases. Even more examples: https://github.com/WasmEdge/wasmedge-db-examples This WasmEdge-based microservice utilizes high-performance non-blocking networking on both the HTTP service & the database client. It is a faster, lighter & more secure alt to Linux container-based microservices.
10 points · Open discussion

MAKE YOURSELF AT HOME

A few shortcuts

/
Search the collection
?
Open this guide
Esc
Close dialogs and navigation

Your saved repositories and interests stay in this browser.