encoding
Fiber
Our great sponsors
encoding | Fiber | |
---|---|---|
8 | 104 | |
962 | 31,381 | |
0.7% | 3.1% | |
3.6 | 9.4 | |
5 months ago | 3 days ago | |
Go | Go | |
MIT License | MIT License |
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.
encoding
- Handling high-traffic HTTP requests with JSON payloads
-
Rust vs. Go in 2023
https://github.com/BurntSushi/rebar#summary-of-search-time-b...
Further, Go refusing to have macros means that many libraries use reflection instead, which often makes those parts of the Go program perform no better than Python and in some cases worse. Rust can just generate all of that at compile time with macros, and optimize them with LLVM like any other code. Some Go libraries go to enormous lengths to reduce reflection overhead, but that's hard to justify for most things, and hard to maintain even once done. The legendary https://github.com/segmentio/encoding seems to be abandoned now and progress on Go JSON in general seems to have died with https://github.com/go-json-experiment/json .
Many people claiming their projects are IO-bound are just assuming that's the case because most of the time is spent in their input reader. If they actually measured they'd see it's not even saturating a 100Mbps link, let alone 1-100Gbps, so by definition it is not IO-bound. Even if they didn't need more throughput than that, they still could have put those cycles to better use or at worst saved energy. Isn't that what people like to say about Go vs Python, that Go saves energy? Sure, but it still burns a lot more energy than it would if it had macros.
Rust can use state-of-the-art memory allocators like mimalloc, while Go is still stuck on an old fork of tcmalloc, and not just tcmalloc in its original C, but transpiled to Go so it optimizes much less than LLVM would optimize it. (Many people benchmarking them forget to even try substitute allocators in Rust, so they're actually underestimating just how much faster Rust is)
Finally, even Go Generics have failed to improve performance, and in many cases can make it unimaginably worse through -- I kid you not -- global lock contention hidden behind innocent type assertion syntax: https://planetscale.com/blog/generics-can-make-your-go-code-...
It's not even close. There are many reasons Go is a lot slower than Rust and many of them are likely to remain forever. Most of them have not seen meaningful progress in a decade or more. The GC has improved, which is great, but that's not even a factor on the Rust side.
-
Quickly checking that a string belongs to a small set
We took a similar approach in our JSON decoder. We needed to support sets (JSON object keys) that aren't necessarily known until runtime, and strings that are up to 16 bytes in length.
We got better performance with a linear scan and SIMD matching than with a hash table or a perfect hashing scheme.
See https://github.com/segmentio/asm/pull/57 (AMD64) and https://github.com/segmentio/asm/pull/65 (ARM64). Here's how it's used in the JSON decoder: https://github.com/segmentio/encoding/pull/101
-
80x improvements in caching by moving from JSON to gob
Binary formats work well for some cases but JSON is often unavoidable since it is so widely used for APIs. However, you can make it faster in golang with this https://github.com/segmentio/encoding.
-
Speeding up Go's builtin JSON encoder up to 55% for large arrays of objects
Would love to see results from incorporating https://github.com/segmentio/encoding/tree/master/json!
-
Fastest JSON parser for large (~888kB) API response?
Try this one out https://github.com/segmentio/encoding it's always worked well for me
-
📖 Go Fiber by Examples: Delving into built-in functions
Converts any interface or string to JSON using the segmentio/encoding package. Also, the JSON method sets the content header to application/json.
-
In-memory caching solutions
If you're interested in super fast & easy JSON for that cache give this a try I've used it in prod & never had a problem.
Fiber
- อย่าเพิ่งใช้ fiber ถ้ายังไม่ได้อ่าน doc
-
Ultimate Guide to User Authorization with Identity Platform
To make my life easier, I added Fiber, a popular lightweight framework. Regardless of which package you use, the process and most of the code will remain unchanged.
-
go for web backend
Since you're from Nodejs just like me, I use fiber https://gofiber.io/ it's easier to understand from a Nodejs background (express, etc) and there's nothing wrong using it if you know it, your casual application wont need all the performance in the world Go provides
-
Which is the best framework to create web apps with go?
I think u should try Fiber it's the fastest according to the benchmarks and imo it's the best I love it!!!
-
Boneless: a CLI to create your apps with Go
Boneless is a powerful tool that offers a wide range of features to facilitate application development. In this blog post, we will explore some essential tools that can be used in conjunction with Boneless: Service Weaver, Go Migrate, SQLC, and Fiber. Let's discover how these tools can boost productivity and efficiency in application development.
-
Integrating OpenAI's GPT-3 into a Next.js and Go Fiber App
Fiber
-
Best and fastest way to learn Golang for web dev?
Fibber is web framework written in Go. It is very easy to learn. https://gofiber.io
-
Hermes. Extremely fast full-text-searches (10-300µs) and cache.
don’t have an API at all - it’s a security vulnerability and unless you already know how to secure an API suite it’s very likely to increase risk for a dependent project. if you’re set on an API, use a well known routing package (e.g I love gofiber), and add an optional .withMiddleware() to your start func to allow clients to extend and secure the API themselves
- What are the possible ways to integrate react and django ?
-
I've just started learning Golang, and I'm struggling to choose a framework.
I have loved using fiber. Very nice API with lots of configurability and it scales very well compared to echo, gin, etc.
What are some alternatives?
sonic - A blazingly fast JSON serializing & deserializing library
Gin - Gin is a HTTP web framework written in Go (Golang). It features a Martini-like API with much better performance -- up to 40 times faster. If you need smashing performance, get yourself some Gin.
groupcache - Clone of golang/groupcache with TTL and Item Removal support
Echo - High performance, minimalist Go web framework
parquet-go - Go library to read/write Parquet files
mux - A powerful HTTP router and URL matcher for building Go web servers with 🦍
base64 - Faster base64 encoding for Go
Iris - The fastest HTTP/2 Go Web Framework. New, modern and easy to learn. Fast development with Code you control. Unbeatable cost-performance ratio :rocket:
buntdb - BuntDB is an embeddable, in-memory key/value database for Go with custom indexing and geospatial support
chi - lightweight, idiomatic and composable router for building Go HTTP services
hilbert - Go package for mapping values to and from space-filling curves, such as Hilbert and Peano curves.
fasthttp - Fast HTTP package for Go. Tuned for high performance. Zero memory allocations in hot paths. Up to 10x faster than net/http