#From nethttp To Fiber
33 messages · Page 1 of 1 (latest)
fiber is http server framework. it does nto provide http client funtionality.
you cant use orange 🍊 to fix a hole on the roof, yes.
Good example lmfao
What about fasthttp, whould that be helpful ? seems like its the only option
fiber use fasthttp.
fasthttp does provide http client. but it only support http1 protocol, which is slower and less efficient that http2.
also fasthttp has very different interface. so you may need to learn all over again.
Actually i didn't , but i'm searching in general to a better/faster way to connect to the destination, and http2 seems to be a slow option. Or maybe i'm just using it wrong?
Uhmm, so its not the sloution at all
It's like 99.9% your infrastructure speed, latency, distance from target
net/http not faster, we already test
He wants a client library
its possible, you can do it if you want to. but consider the cost.
What do you guys suggest to get faster response and faster benchmarks if its not net/http
And if you agree on net/http how can i get the most of it
What are you trying to optimize? Are you having speed issues?
Yeah i'm having a bit of a speed issues tbh
about faster, will you be able to reach that limit? where the different really matter.
you most likely wont spawn thousands of concurrent http request.
Well its about the delay, i use thrift if you are familliar with it. Which has bunch of delays that's pretty tricky to avoid, so i thought a faster connection could help with that 🤔
yes we net speed fast for it..
idk what this sentence means
IDK it's like trying to run faster by tying your shoes differently. if you're not serving stuff, and don't have thousands of concurent requests, i think net/http is good. Your infra and your destination's infra is responsible for the response speed
what do you think we can use to speed up thrift
Idk what thrift is
like apache
I am 100% sure net/http is not the bottleneck in your system