Our great sponsors
-
So my question is - why does http4s have already ~3 years of development time for its 1.0 version? Also bonus question - why does it have such a poor performance in these benchmarks? I know that those aren't everything but the difference is very huge and I would like to know if there is a post or comment somewhere(or anything) from a person that did a deep dive into it and could explain why the performance is what it is. Also, can anyone share an experience of using http4s in a prod environment? What are the specs of vm it needs to handle 1000 rps?
-
You can use async-profiler to see what is happening under the hood.
-
WorkOS
The modern identity platform for B2B SaaS. The APIs are flexible and easy-to-use, supporting authentication, user identity, and complex enterprise features like SSO and SCIM provisioning.
-
Those benchmarks are using a snapshot version of cats-effect. I don't know where that one comes from, but previously they were using a snapshot from https://github.com/typelevel/cats-effect/pull/3332 which had some issues (3.5-6581dc4, 70% performance degradation), which have since been resolved (see that PR for more info and comparative benchmarks).
