microservice-rust-mysql
spec
microservice-rust-mysql | spec | |
---|---|---|
14 | 48 | |
338 | 2,836 | |
1.2% | 4.9% | |
5.9 | 7.0 | |
5 days ago | 5 days ago | |
Rust | ||
Apache License 2.0 | Creative Commons Attribution 4.0 |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
microservice-rust-mysql
-
Release: WasmEdge 0.12 and 0.12.1
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
- A Rust Microservice Demo with MySQL CRUD Support
- A Rust Microservice demo with MySQL CRUD Support, Compiled to WebAssembly and Running on WasmEdge - A Secure and Lightweight Alternative to Linux containers
- A Rust Microservice with MySQL CRUD Support, Compiled to WebAssembly and Running on WasmEdge - A Secure and Lightweight Alternative to Native Compilation in Containers natively compiled Rust apps in Linux containers, can be run by Docker Podman, K8s etc
-
Rust microservices in server-side WebAssembly
The example below, from the microservice-rust-mysql demo app, shows how to create a web server in hyper for WasmEdge. The main listening loop of the web server is as follows:
spec
-
Show HN: Lapdev, a new open-source remote dev environment management software
Hi, Lapdev dev here. Let me try to answer your question.
It's installed on a remote server so it provides remote environments. If you use VSCode remote, then you can "open" it through VSCode remote ssh.
The environment that Lapdev provides essentially is a container (other format is on the roadmap) with things pre-installed as defined in Devcontainer(https://containers.dev/) format.
-
Show HN: Flox 1.0 – Open-source dev env as code with Nix
Happy to take this one, as I am one of the cofounder of Daytona.
Daytona solves all the automation and provisioning of the dev environment, actually wrote an article here laying out exactly what we do: https://www.daytona.io/dotfiles/diy-guide-to-transform-any-m...
Daytona currently supports only the dev container (https://containers.dev/) "dev env infrastructure as code" standard, but are looking to support others such as devfile, nix and flox.
Hope this helps
-
A Journey to Find an Ultimate Development Environment
The full usage of the container means that you'll do the development inside the container. All the tools for development need to be installed inside the container. One of the technologies that leverage this approach is Devcontainers.
-
How CDEs work - no bs blog post
Two standards for CDE configuration exist: devfile.yml and devcontainer.json. Both assume that the CDE is a single container and allow specification of which tools should be deployed to this container, as well as a reference to scripts that should run after the container has been created.
- Use Docker to create a local development Python environment
-
Launching dev containers from code - is impossible?
... is how I introduced the concept of dev containers in my last article.
-
Dev Containers: Open, Develop, Repeat...
How it works? Dev Containers is a specification based on Docker. This specification describes a metadata file (devcontainer.json), which defines how the project (Docker container, IDE settings, plugins, etc) is set up.
-
Try MongoDB and Laravel in 1-click via GitHub Codespaces
Codespaces is built to run Dev Containers, an open standard for Development Containers. The Dev Container will reference a Docker build file, which describes the software and services our app is running on. It also defines things related to our development environment, including IDE plugins, network ports, and more.
-
Is there some catch to cause DNS issues on Linux, that is not common with Windows or Mac?
I was using Devcontainer with VS Code. In a part of the container build process, DNS lookup seemed to be failing in Debian 12. BTW, the container image was based on Debian 11. I probably tried it about 10 times in total, so I'm pretty sure it persisted, not an one time error. I noticed the build process was failing because the process failed to find some domains, with an error message like could not resolve host github.com. Some domains I noticed was github.com and ghcr.io, so it failed sometimes for one domain, and sometimes for the other.
-
Dev Container for React Native with Expo
// For format details, see https://aka.ms/devcontainer.json. For config options, see the // README at: https://github.com/devcontainers/templates/tree/main/src/typescript-node { "name": "Node.js & TypeScript", // Or use a Dockerfile or Docker Compose file. More info: https://containers.dev/guide/dockerfile "image": "mcr.microsoft.com/devcontainers/typescript-node:1-20-bullseye", // Features to add to the dev container. More info: https://containers.dev/features. // "features": {}, // Use 'forwardPorts' to make a list of ports inside the container available locally. "forwardPorts": [8081], "initializeCommand": "bash .devcontainer/initializeCommand.sh", // Use 'postCreateCommand' to run commands after the container is created. "postCreateCommand": "bash .devcontainer/postCreateCommand.sh", // Configure tool-specific properties. // "customizations": {}, // Uncomment to connect as root instead. More info: https://aka.ms/dev-containers-non-root. // "remoteUser": "root", // "containerEnv": { // }, // "remoteEnv": { // "DEV_USER_HOST": "${localEnv:USERNAME}" // }, "runArgs": ["-p=8081:8081", "--env-file", ".devcontainer/.env"] }
What are some alternatives?
postgres-wasm - A PostgresQL server running in your browser
features - A collection of Dev Container Features managed by Dev Container spec maintainers. See https://github.com/devcontainers/feature-starter to publish your own
webvm - Virtual Machine for the Web
features - A collection of development container 'features' for machine learning and data science
SSVM - WasmEdge is a lightweight, high-performance, and extensible WebAssembly runtime for cloud native, edge, and decentralized applications. It powers serverless apps, embedded functions, microservices, smart contracts, and IoT devices.
conda-devcontainer-demo - Mini Conda + Mamba dev container setup to make working with environments easy.
podman-wasm
tweek - Tweek - an open source feature manager
dapr-wasm - A template project to demonstrate how to run WebAssembly functions as sidecar microservices in dapr
lapdev - Self-Hosted Remote Dev Environment
postgres-wasm - A PostgresQL server in your browser
devbox - Instant, easy, and predictable development environments