pekko
grpc_bench
pekko | grpc_bench | |
---|---|---|
8 | 58 | |
1,074 | 854 | |
4.8% | - | |
9.7 | 8.4 | |
7 days ago | 20 days ago | |
Scala | Dockerfile | |
Apache License 2.0 | 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.
pekko
-
Is akka still worth learning to be employable?
Pekko is open source, has the same API. So there's no problem there.
- Migrate the classic transport of pekko to Netty 4 without CVEs
-
6 Common Misconceptions Around Akka-HTTP / Pekko-HTTP
Understandable considering the size of Pekko and how much time is passed, I would recommend asking any questions/concerns on either the Pekko mailing list https://lists.apache.org/[email protected] or on Github discussions https://github.com/apache/incubator-pekko/discussions.
-
Reconnecting with Scala. What's new?
Another big reason behind the "struggle" is we have done further improvements. For example the first release of Pekko will support all Scala versions from 2.12 up to 3.3.0 LTS (which was just released a couple of days ago). This also includes Pekko's modules which means we had to either add back in Scala 2.12 support or Scala 3 support. Yet another example would be https://github.com/apache/incubator-pekko/pull/281 which allowed us to drop scala-java8-compat dependency for Scala 2.13 or higher. So while these improvements aren't technically necessary, they have a large impact on Pekko going forward, i.e. the scala-java8-compat change means that we can drop Scala 2.12 at any point in time without breaking users.
-
Scala opensource projects
Apache Pekko is the open source fork of Akka. I know they can use more hands right now - https://github.com/apache/incubator-pekko/issues
-
What is the current status of Akka in your organisation?
There is an option missing: Considering switching to pekko when it's ready: https://github.com/apache/incubator-pekko
-
Stop Building on Corporate-Controlled Languages
- In 2022, Lightbend changed the Akka licence, made it proprietary and very expensive at large scale
Software that starts out as more "pure", non-corporate open-source can still turn the tables on you and charge large licensing fees later. But at least if it's open source from the start, it can be forked, e.g. for Akka, there's this Apache fork that was started after Akka changed its licence: https://github.com/apache/incubator-pekko . This is the key open source protection, and it's true for both corporate and non-corporate projects.
grpc_bench
-
Poor gRPC performance on test - help needed
SayHello, GetUser, and Sum differ only by payload size. Sum is the simplest one - (int, int) -> int, GetUser is (long) -> User (medium payload), and SayHello uses exactly the same payload as this test: https://github.com/LesnyRumcajs/grpc_bench/tree/master/dotnet_grpc_bench
-
2023-06-25 gRPC benchmark results
This is correct. The problem is not with the benchmark itself but with the implementation. If you look at the result, you can see that even with 6 "allowed" CPUs, the vertx server utilizes less than 100%. Apparently, the current vertx implementation (the one implemented in https://github.com/LesnyRumcajs/grpc_bench/tree/master/java_vertx_grpc_bench) is single-threaded or has some other limitation.
Another iteration of grpc_bench!
-
Why does C#/.NET is in demand in Philippines especially in BGC? How about PHP?
Because it's fast and runs on Windows, Linux, and MacOS
- .NET Core performance on Linux
-
Another two cents about the current situation with the Scala user base and economics.
In general though, akka/pekko-streams are known to be one of the fastest implementations out there. Their grpc client for example even beats languages like Rust (see https://www.lightbend.com/blog/akka-grpc-update-delivers-1200-percent-performance-improvement and https://github.com/LesnyRumcajs/grpc_bench/wiki/2022-03-15-bench-results).
-
What is the current status of Akka in your organisation?
The whole point I was making is at least up until 8 months ago (at best, I can't commend on the stability/maturity/performance of shardcake) Akka was the only mature library/ecosystem solving this problem with also a very strong focus on performance (for example still to this day, akka/pekko-grpc is generally one of the fastest grpc implementations I am aware of, its even beating rust if you have at least 2 cores (see https://github.com/LesnyRumcajs/grpc_bench/wiki/2022-03-15-bench-results)
-
QuickBuffers 1.1 released
It would be interesting to create a new java benchmark with your implementation.
-
Ask HN: Examples of Top C# Code?
Also worth checking out the gRPC benchmarks: https://github.com/LesnyRumcajs/grpc_bench/discussions/284
dotnet is up there with Rust.
What are some alternatives?
zio-akka-cluster - ZIO wrapper for Akka Cluster
eCAL - Please visit the new repository: https://github.com/eclipse-ecal/ecal
ZIO - ZIO — A type-safe, composable library for async and concurrent programming in Scala
FlatBuffers - FlatBuffers: Memory Efficient Serialization Library
Scala Native - Your favorite language gets closer to bare metal.
gRPC - The C based gRPC (C++, Python, Ruby, Objective-C, PHP, C#)
scala-cli - Scala CLI is a command-line tool to interact with the Scala language. It lets you compile, run, test, and package your Scala code (and more!)
gRPC - The Java gRPC implementation. HTTP/2 based RPC
Play - The Community Maintained High Velocity Web Framework For Java and Scala.
greeter-bpf - implementing gRPC GreeterServer in eBPF just for fun.
nim-sqlite3-abi - SQLite3 wrapper
ghz - Simple gRPC benchmarking and load testing tool