go-wasm
serviceq
| go-wasm | serviceq | |
|---|---|---|
| 2 | 3 | |
| 54 | 74 | |
| - | - | |
| 0.0 | 2.6 | |
| almost 3 years ago | 5 months ago | |
| JavaScript | Go | |
| - | Apache License 2.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.
go-wasm
-
Open source Go projects to contribute (beginners)
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)
-
Intro to Go<>WebAssembly and related experiments
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.
serviceq
-
Open source Go projects to contribute (beginners)
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)
-
Looking for an open-source Golang project to work on
If interested in load balancers/proxies and networking in general, you may want to look at https://github.com/gptankit/serviceq.
-
I'm trying to create a load balancer that routes based on CPU availability on server. Do you guys know the best algorithm for such a case?
When you have so many metrics to consider, ideal choice is to assign weights to each metric and let the load balancer distribute load probabilistically (think weighted random). Implemented a load balancer in Go on similar lines (https://github.com/gptankit/serviceq) by calculating 'effective error' as weight from each node and inversely distributing load to the cluster. This ensures that a) one single node doesn't get overwhelmed with all the requests and b) even if some node is down, it keeps receiving a small percentage of requests (albeit lesser and lesser as time progresses).
What are some alternatives?
h3-js - h3-js provides a JavaScript version of H3, a hexagon-based geospatial indexing system.
enpass-cli - Enpass commandline client
fyne - Cross platform GUI toolkit in Go inspired by Material Design
Gokapi - Lightweight selfhosted Firefox Send alternative without public upload. AWS S3 supported.
go-json - Fast Go JSON encoder for large arrays of objects
dsq - Commandline tool for running SQL queries against JSON, CSV, Excel, Parquet, and more.
go2ts - Online Golang Struct to TypeScript Interface Converter
hakrawler - Simple, fast web crawler designed for easy, quick discovery of endpoints and assets within a web application
Porcupine - On-device wake word detection powered by deep learning
reddit-rss - improved rss feed for reddit
Benthos - Fancy stream processing made operationally mundane
dbmigrat - DB schema migration lib designed for monorepos.