Our great sponsors
|about 1 year ago||1 day ago|
|Apache License 2.0||GNU General Public License v3.0 or later|
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.
A Look at Performance in Wasmtime and Cranelift
9 projects | /r/rust | 6 Sep 2022
The bytecode alliance had the lucet project which would be an OS executing WASM application, enabling very strict sandboxing.
Your python 4 dream list.
7 projects | /r/Python | 21 Feb 2022
References for anyone following: wasmtime Lucet
There are a *lot* of actor framework projects on Cargo.
17 projects | /r/rust | 1 May 2021
I guess lucet could be an under-layer for this but it's not really the same, different levels of the stack. Fascinating.
Writing Rust the Elixir way
5 projects | dev.to | 26 Nov 2020
I also want to use this opportunity to say a big thank you to the teams working on Rust, Wasmer, Wasmtime, Lucet and waSCC. It would be impossible to build Lunatic without all the hard work put into this projects.
What are the current hot topics in type theory and static analysis?
15 projects | /r/ProgrammingLanguages | 8 May 2023
First-class distributed and multicore computing. Swift has first-class “actors” and “distributed” methods. Unison, Erlang, and Elixir are built with distributed being one of the #1 concerns. Though first-class is not super common and I don't really expect it to be because usually libraries are enough (e.g. Scala has Akka and is used WIDELY for distributed); whereas something like linear types and typed effects, you can't emulate in a library.
Anything close beam/otp for other languages?
7 projects | /r/elixir | 7 Apr 2023
Akka is a library that implements the actor model for JVM languages. Mainly in Scala, but you can use it in Java too, and maybe others. It doesn't feel as ergonomic as Elixir, but if Elixir is too "out there" for the decision makers in your case, this might be a friendlier alternative.
Carl Hewitt has died [pdf]
5 projects | news.ycombinator.com | 6 Jan 2023
About Elixir and the microservices architecture
3 projects | dev.to | 14 Dec 2022
Note Akka, the Java & friends framework, is working with the actor model and have as main inspiration Erlang to mimic some features of the BEAM on top of the JVM.
Akka will no longer be Open Source
2 projects | dev.to | 10 Sep 2022
If I hear about Actor model, the first thing that comes to my mind is the popular Open Source library Akka.2 projects | dev.to | 10 Sep 2022
Lightbend, the company owning Akka, recently shared a blog post signed by the CEO announcing a license change from Apache 2.0 to Business Source License 1.1, a proprietary license. You can already find it in this PR, merged a couple days ago.
Why We Are Changing the License for Akka
2 projects | /r/scala | 7 Sep 2022
Akka 2.6 is on the open source Apache license, that is unchanged (its not possible for Lightbend to change an existing license). Its only the new Akka 2.7 which has the BSL license, so as long as you don't upgrade you are fine. See https://github.com/akka/akka/pull/31561.
We Are Changing the License for Akka
Here is Akka's dependency specification: https://github.com/akka/akka/blob/main/project/Dependencies....
How many of these would have to opt for this source available approach before Akka would no longer be sustainable?
I don't think that the Akka change is aimed at cloud providers. Akka is a toolkit for building highly concurrent, distributed, and resilient message-driven applications for Java and Scala . It's not possible for AWS to offer their own "Akka service" the way they offered Redis through ElastiCache. This change affects companies that build software using Akka, many of which may not be software-focused. For example, here's a case study of an oilfield services company that uses Akka:
 As found on https://akka.io/
> So Amazon can take free code, sell it as a slickly-packaged service, and not need to share anything.
Right, because they didn't change it. So what would there be to share anyway? 'Go to https://github.com/akka/akka'?
> but it does mean that at least every user has access to the code to make their "Akka Service" as good as Amazon's.
That code is meaningless. In this scenario we already established that Amazon is selling an unmodified copy of Akka as a Service (which, by the way, we will revisit this point later). And we already established, in your own words, that it's not about the code:
> Their secret sauce is "we have a Borg Cube's worth of datacenters, so we can run the same code as you at a lower price".
So what would the SSPL require, they publish their deployment scripts to their cloud datacentres? Like I said, that's meaningless.
> "Akka Service"
Final point. There's no such thing as an 'Akka Service'. Akka is a bunch of libraries. You link it into your JVM application. You don't run Akka separately, so by definition you can't offer it as a service (even if you're Amazon).
Hence my suggestion of AGPL, and heck let's be generous, let's add a commercial use exception for businesses with less than $20m revenue, similar to what they're doing now with the BSL. Except with my suggestion the software would stay as strong copyleft, most businesses would be happy with the commercial use exception, and a few would have to pay their fair share.
What are some alternatives?
Vert.x - Vert.x is a tool-kit for building reactive applications on the JVM
Apache ZooKeeper - Apache ZooKeeper
Hazelcast - Open-source distributed computation and storage platform. Real-time Stream Processing Unconference. Save Your Spot https://hazelcast.com/lp/unconference/
Hystrix - Hystrix is a latency and fault tolerance library designed to isolate points of access to remote systems, services and 3rd party libraries, stop cascading failure and enable resilience in complex distributed systems where failure is inevitable.
JGroups - The JGroups project
Atomix - A Kubernetes toolkit for building distributed applications using cloud native principles
Lagom - Reactive Microservices for the JVM
Apache Storm - Mirror of Apache Storm
Finagle - A fault tolerant, protocol-agnostic RPC system
Orbit - Orbit - Virtual actor framework for building distributed systems
Elixir - Elixir is a dynamic, functional language for building scalable and maintainable applications
Quasar - Fibers, Channels and Actors for the JVM