go-wasm VS core

https://github.com/gptankit/serviceq - a load balancer and queue (need http2 support) https://github.com/gptankit/go-wasm - wasm experiments in go (if you want to help community adapt to wasm using go)

Wrote an article detailing on how WebAssembly (wasm) fits into the world of Go -> https://github.com/gptankit/go-wasm/. Have tried to give all the information necessary to get started with generating WebAssembly from Go and subsequent consumption in Javascript.

As a recap, StaticBackend is a simple backend server API easy to self-host or importable in Go program without hosting a separate server.

StaticBackend is a simple backend server API you may use to build complex web applications. Fully open source and easy to self-host. It handles lot of backend building blocks.

I want to put StaticBackend on your radar. It's an open-source backend API I've worked on for more than 3.5+ years.

I'd like to put StaticBackend - GitHub in your radar. It's a simple backend server API that tries to handle most of the common functiionalities found in web applications. It's open-source and very easy to self-host.

Since people often ask where they could contribute to a Go project, I thought I'd jump in as I took some times to create some good first contribution issues for StaticBackend.

It's not always present in issues what has to be done in a project. On that note, I'd shamelessly suggest to look at StaticBackend which is a backend API to help expedite v1 (MVP) launch time.

I can tell you what I like and don't like about my open source backend API (self-hosted Firebase) https://github.com/staticbackendhq/core

Hey, if you're interested in web backend I started StaticBackend - GitHub repo in 2019. It's a REST backend server which aim to provide most of the common building blocks like user authentication, database, file storage, websocket, schedule tasks, server-side function.